KDFONTOP/PIO_UNIMAPCLR: Input/output error

[Ludovic Courtès]

Hello Danny & all,

Danny Milosavljevic <address@hidden> 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:

--- 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))

Sounds good?

Ludo’.