https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c47
Stanislav Brabec changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |REOPENED
InfoProvider|sbrabec@suse.com |
--- Comment #47 from Stanislav Brabec 2012-07-04 15:41:12 CEST ---
Well, I see two potential problems:
1. There is no dependence between systemd-vconsole-setup.service and
sys-devices-virtual-tty-tty*.device. These devices are started to be
initialized just after remount-rootfs.service finishes (both
remount-rootfs.service and systemd-vconsole-setup.service start at the same
time, but time of its completion is not deterministic).
There is a potential race condition:
Important parts of systemd-vconsole-setup.service don't finish before
sys-devices-virtual-tty-tty*.device and:
- /run/numlock-on is set after calling setleds udev rule.
- setleds is called in parallel with something else in
systemd-vconsole-setup.service and
2. There is a race condition in kbd utilities and parallel calling may cause
undefined behavior (one of possible explanations of bug 769423).
1. See "systemd-analyze plot >boot-numlock-failed.svg" output. There is no
synchronization. virtual-tty-tty*.device should depend on
systemd-vconsole-setup.service.
2. Not easy to debug or reproduce.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.