[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: KDFONTOP/PIO_UNIMAPCLR: Input/output error

From: Ludovic Courtès
Subject: Re: KDFONTOP/PIO_UNIMAPCLR: Input/output error
Date: Thu, 05 Jul 2018 00:20:49 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

address@hidden (Ludovic Courtès) skribis:

> Danny Milosavljevic <address@hidden> skribis:
>>> PIO_UNIMAPCLR: Input/output error
>>> 3) PIO_UNIMAPCLR: Input/output error
>>> Anything to worry about?
>> According to 
>> 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

I think I have a plausible explanation.  :-)  The EIO comes from
‘hung_up_tty_ioctl’ in drivers/tty/tty_io.c.  This is because mingetty
would call ‘vhangup’, and presumably, there was a time window where
‘setfont’ would find itself talking to a hung-up terminal.  QED.

Anyway, in commit a043b5b81a080c47e24298c80857919b9ea21bb2 I’ve added
--nohangup to mingetty and now ‘setfont’ is happy, and so am I.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]