From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: KDFONTOP/PIO_UNIMAPCLR: Input/output error
Date: Wed, 04 Jul 2018 16:10:18 +0200 [thread overview]
Message-ID: <874lhfccs5.fsf_-_@gnu.org> (raw)
In-Reply-To: <20180703152752.50f1795e@scratchpost.org> (Danny Milosavljevic's message of "Tue, 3 Jul 2018 15:27:52 +0200")
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
Hello Danny & all,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
>> PIO_UNIMAPCLR: Input/output error
>> 3) PIO_UNIMAPCLR: Input/output error
>>
>> Anything to worry about?
>
> According to https://elixir.bootlin.com/linux/v3.2/source/include/linux/kd.h#L70
> that's trying to clear the Unicode -> font map (that is, charmap).
>
> In Linux, ./drivers/tty/vt/vt_ioctl.c implements it.
>
> Can't see how that ever ends up in -EIO O_o
Sometimes we also get:
putfont: KDFONTOP: Input/output error
In both cases, the warning comes from the ‘setfont’ program, invoked
from ‘console-font-shepherd-services’.
I’ve looked at the code and man pages and like you, I don’t see where
EIO comes from. Maybe it’s a generic ioctl error that’s return before
we reach the actual ioctl implementation in the VT driver, sorta like
EBADF?
Until we find out, I’d like to just silence the warnings:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 841 bytes --]
--- a/gnu/services/base.scm
+++ b/gnu/services/base.scm
@@ -754,8 +754,10 @@ to add @var{device} to the kernel's entropy pool. The service will fail if
;; systemd's vconsole support, let's not treat
;; this as an error.
(case (status:exit-val
- (system* #$(file-append kbd "/bin/setfont")
- "-C" #$device #$font))
+ (with-error-to-port (%make-void-port "w")
+ (lambda ()
+ (system* #$(file-append kbd "/bin/setfont")
+ "-C" #$device #$font))))
((0 71) #t)
(else #f))))
(stop #~(const #t))
[-- Attachment #3: Type: text/plain, Size: 28 bytes --]
Sounds good?
Ludo’.
next prev parent reply other threads:[~2018-07-04 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 8:15 Installation-Protocol for GuixSD x86_64 v0.15-preview Björn Höfling
2018-07-03 10:49 ` Tobias Geerinckx-Rice
2018-07-03 11:38 ` (Ab?)using aliases to set ls' and others' colours Tobias Geerinckx-Rice
2018-07-04 18:01 ` Björn Höfling
2018-07-04 22:17 ` Ludovic Courtès
2018-07-04 22:17 ` Ricardo Wurmus
2018-07-04 17:56 ` Installation-Protocol for GuixSD x86_64 v0.15-preview Björn Höfling
2018-07-03 13:20 ` Marius Bakke
2018-07-03 13:27 ` Danny Milosavljevic
2018-07-03 21:35 ` Ludovic Courtès
2018-07-04 14:10 ` Ludovic Courtès [this message]
2018-07-04 14:29 ` KDFONTOP/PIO_UNIMAPCLR: Input/output error Marius Bakke
2018-07-04 22:20 ` Ludovic Courtès
2018-07-03 21:42 ` Installation-Protocol for GuixSD x86_64 v0.15-preview Ludovic Courtès
2018-07-04 18:06 ` Björn Höfling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lhfccs5.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).