Mailinglist Archive: opensuse-bugs (4233 mails)

< Previous Next >
[Bug 1020327] [Build 20170116] openQA test fails in consoletest_finish
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 18 Jan 2017 16:15:56 +0000
  • Message-id: <bug-1020327-21960-hwi0yjIwsi@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1020327
http://bugzilla.opensuse.org/show_bug.cgi?id=1020327#c10

--- Comment #10 from Fabian Vogt <fvogt@xxxxxxxx> ---
(In reply to Franck Bui from comment #7)
Ok, here's my best bet:

Since systemd v232, systemd-vconsole-setup.service has no more the
RemainAfterExit=true property.

Since plymouth-start.service has Wants=systemd-vconsole-setup.service, the
later is now started several time within the initramfs: it's pulled in by
initrd.target
and by initrd-switch-root.target. And during the second time vconsole-setup
is configuring tty7, which was probably already activated by plymouth-start.

This explains why cryptlvm succeeds, as systemd-vconsole-setup fails there and
thus it does not confuse plymouth.


This has the bad effect to "confuse" plymouth as vconsole-setup is now
configuring tty7 after plymouth started using it. This makes actually
plymouth crashes.

The crashes may happen either right before switching to the rootfs or after.
If the former then systemd will start it again after switching to the new
rootfs otherwise it won't.


Now regarding KDM, not sure if it's expected but it selects:

- tty7 if plymouth is not running (IOW if it crashed after switching
to new rootfs)

- tty8 if plymouth is running (IOW if plymouth crashed before switching
to the new rootfs)

So far I haven't seen plymouthd crash during tests.

Plymouth is running in *both* cases ("plymouth is running" is printed with
systemd 228 and 232)
and kdm selects tty8 because tty7 is blocked by plymouth but not active (as it
got confused).

From that, there're a couple issues:

- why does plymouth-start.service wants systemd-vconsole-setup.service:
I don't see the point as vconsole-setup will automatically configure
any tty detected by udev ?

Probably due to ordering. While plymouth is running, the active ttys can't be
configured. However, every tty has to be configured, so this needs to happen
*before* plymouth starts.

- systemd-vconsole-setup.service is embedded in initramfs and this doesn't
seem to be needed.

It is because of above. There are various bug reports about wrong keyboard
layout
if systemd-vconsole-setup fails during the initrd phase.

- why does plymouth crash in this case (might be fixed in plymouth
git repo as Fabian reported a better behavior on IRC) ?

I will try that again with everything set to the default and plymouth from git
master.

- Why does KDM select either tty7 or tty8 ? in both case tty7 seems to
have been activated by plymouth ?

kdm does not get tty7 (or does not consider it as valid answer) when asking
plymouth for its active vt.
So it chooses to try the next one instead. This is good as using tty7 would
probably fail here.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References