Red Hat Bugzilla – Bug 699282
kbd needs to open ttys in a loop guarding for EIO, due to BKL removal in the kernel.
Last modified: 2012-08-07 16:06:56 EDT
Description of problem:
After system boot up, I've switched to console (Ctrl-Alt-F2), login and run mc (Midnight Commander) or another application with Russian symbols.
Russian symbols not displayed, again. Like this was in Fedora 12.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot system
2. switch to console
3. run application with Russian symbols, as example LANG=ru_RU.UTF-8 mc
White squares instead Russian symbols.
Russian symbols displayed correctly.
I've find workaround or patch.
If I change this line in /lib/udev/rules.d/10-console.rules:
then Russian symbols displayed correctly.
In earlier dracut (in F14) initramfs image contained system binary /lib/udev/console_init from initscripts. Maybe it is the second way to fix this problem:
systemd-vconsole should be responsible for setting that up.
Does invoking /lib/systemd/systemd-vconsole-setup manually make things work for you?
What is the content of /etc/sysconfig/i18n?
Yes, after run /lib/systemd/systemd-vconsole-setup in console Russian symbols displayed correctly.
Which systemd version is this?
Normally /lib/systemd/systemd-vconsole-setup should run at boot.
Can you do "systemctl --full | grep vconsole" after boot when the problem happened and paste the output here?
# yum list installed systemd*
systemd.x86_64 25-1.fc15 @updates-testing
systemd-units.x86_64 25-1.fc15 @updates-testing
I've booted and checked what problem still persist.
# systemctl --full | grep vconsole
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
Can you boot with "rd.plymouth=0"? Do the fonts appear correctly then?
Yes, with rd.plymouth=0 kernel parameter the fonts appear correctly.
Hmm, Ray, have you heard of such a problem with font loading and Plymouth colliding?
OK, my guess is that this might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/comments/245
i.e. setfont should probably retry opening /dev/tty0 a couple of times.
Tentatively reassigning this to kbd. The EIO loop is definitely necessary in kbd. It might fix this problem. If it doesn't feel free to reassign back.
kbd maintainers, can you please beef up open_a_console() in src/getf_fd.c to loop a couple of times if you get EIO when opening the device? Since the BKL was dropped in the kernel this is unfortunately necessary in userspace to make things work race-freely, see the linked ubuntu bug.
We do a similar loop in systemd:
(In reply to comment #8)
> Hmm, Ray, have you heard of such a problem with font loading and Plymouth
vconsole setup needs done before plymouth sets the terminal to graphics mode/the framebuffer driver is loaded, IIRC.
(font/unicode state is per-VT, but inherited from the prior existing console)
OK, will duplicate against dracut then, which apparently dropped the font loading.
Harald, please add an invocation of systemd-vconsole-setup to dracut, before you run plymouth, as discussed on IRC the other day.
Created attachment 496750 [details]
I was not able to reproduce the problem, but I patched kbd check EIO and loop - anyone willing to test it?
SRPM and x86_64 Fedora 15 build is available here:
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: