From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: KDFONTOP/PIO_UNIMAPCLR: Input/output error Date: Thu, 05 Jul 2018 00:20:49 +0200 Message-ID: <87in5ubq2m.fsf@gnu.org> References: <20180703101553.702b0b00@alma-ubu> <20180703152752.50f1795e@scratchpost.org> <874lhfccs5.fsf_-_@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50820) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1faq8q-0000O9-8r for guix-devel@gnu.org; Wed, 04 Jul 2018 18:20:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1faq8p-00088t-3S for guix-devel@gnu.org; Wed, 04 Jul 2018 18:20:52 -0400 In-Reply-To: <874lhfccs5.fsf_-_@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Wed, 04 Jul 2018 16:10:18 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: guix-devel ludo@gnu.org (Ludovic Court=C3=A8s) skribis: > Danny Milosavljevic skribis: > >>> PIO_UNIMAPCLR: Input/output error >>> 3) PIO_UNIMAPCLR: Input/output error >>>=20 >>> 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 =E2=80=98setfont=E2=80=99 progr= am, invoked > from =E2=80=98console-font-shepherd-services=E2=80=99. > > I=E2=80=99ve looked at the code and man pages and like you, I don=E2=80= =99t see where > EIO comes from. Maybe it=E2=80=99s a generic ioctl error that=E2=80=99s = return before > we reach the actual ioctl implementation in the VT driver, sorta like > EBADF? I think I have a plausible explanation. :-) The EIO comes from =E2=80=98hung_up_tty_ioctl=E2=80=99 in drivers/tty/tty_io.c. This is becau= se mingetty would call =E2=80=98vhangup=E2=80=99, and presumably, there was a time wind= ow where =E2=80=98setfont=E2=80=99 would find itself talking to a hung-up terminal. = QED. Anyway, in commit a043b5b81a080c47e24298c80857919b9ea21bb2 I=E2=80=99ve add= ed --nohangup to mingetty and now =E2=80=98setfont=E2=80=99 is happy, and so a= m I. Ludo=E2=80=99.