Red Hat Bugzilla – Bug 460565
plymouth gets confused by an additional serial console
Last modified: 2008-11-10 15:30:33 EST
Description of problem:
boot with a kernel commandline suitable for serial debugging e.g containing
observe plymouth --show-splash from the initrd stop and do nothing, just echoing typed characters to the console. Ctrl-Alt-Del to reboot.
Version-Release number of selected component (if applicable):
ah, I thought I stamped out the serial console bugs. I'll take a look.
*** Bug 460890 has been marked as a duplicate of this bug. ***
I think this should work a lot better in
I'm going to close this bug, but if you still have problems please reopen it.
I don't normally use a serial console so there may be other plymouth integration issues lurking.
Still some issues when started with the usual console=ttyS0,115200 console=tty0
- if the serial console is not connected it just sits there waiting, with some errors about ttyS0 (don't have the log right now). Whenever the console is attached the boot process continues
- with console attached it sends all init messages there and nothing on tty0, thats not what I figure should happend if I am reading Documentation/serial-console.txt correctly. Expect the messages on both consoles.
Still not working for me with
The boot hangs after
"plymouthd used greatest stack depth: 4736 bytes left"
(In reply to comment #5)
> Still not working for me with
> The boot hangs after
> "plymouthd used greatest stack depth: 4736 bytes left"
Btw, this is with a normal single console=ttyS0,115200 and a connected device.
And I need this to be able to work effectively.
with plymouth-0.6.0-0.2008.09.05.4 here it seems like back to square one, the symptoms are the same as in my original filing, regardless of the console being connected or not.
A single console=ttyS0,115200 works as expected.
*** Bug 461601 has been marked as a duplicate of this bug. ***
Yanko pointed me at this bug after I opened bug 461601. I had been having trouble with new kernels since the -287 series. I assumed that it was a kernel problem, but now I think that plymouthd might have been the culprit.
I did a yum update this morning and got a plymouth update + a new kernel (and yum did install them in that order, according to the logs). The new kernel would not boot, hanging soon after the "plymouthd used greatest stack depth" warning. I ended up uninstalling plymouth packages and reinstalling them (via yum remove and yum install), and then regenerating the initrd for the kernel. Now the kernel boots successfully.
As to why uninstalling and reinstalling plymouth would matter, I'm not sure.
you probably went from
which fixed a buggy loop
Looks like the previous version of plymouth was:
Aug 29 07:12:15 Updated: plymouth-0.6.0-0.2008.08.27.2.fc10.x86_64
But I'm not sure that that explains what I saw. Here's a snippet from my yum log this morning. plymouth is updated to the new version:
Sep 09 07:24:35 Updated: libXft-devel-2.1.13-1.fc10.x86_64
Sep 09 07:24:37 Updated: plymouth-libs-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 07:24:38 Updated: plymouth-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 07:24:39 Updated: plymouth-plugin-spinfinity-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 07:24:39 Updated: plymouth-plugin-label-0.6.0-0.2008.09.05.3.fc10.x86_64
...new kernel is installed and rpm is updated. At this point -314 would hang at boot time.
Sep 09 07:26:00 Installed: kernel-2.6.27-0.314.rc5.git9.fc10.x86_64
Sep 09 07:26:00 Updated: rpm-4.5.90-0.git8461.5.x86_64
...after I read Yanko's comments, I tried removing plymouth (thinking it might be an optional component):
Sep 09 09:59:24 Erased: mkinitrd
Sep 09 09:59:24 Erased: plymouth-plugin-spinfinity
Sep 09 09:59:26 Erased: plymouth
Sep 09 09:59:26 Erased: plymouth-plugin-label
Sep 09 09:59:27 Erased: plymouth-libs
...plymouth is removed. But looks like mkinitrd depends on it, so I reinstalled it:
Sep 09 10:00:16 Installed: mkinitrd-6.0.62-1.fc10.x86_64
Sep 09 10:00:16 Installed: plymouth-libs-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 10:00:17 Installed: plymouth-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 10:00:18 Installed: plymouth-plugin-spinfinity-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 10:00:19 Installed: plymouth-plugin-label-0.6.0-0.2008.09.05.3.fc10.x86_64
After this, I tried rebuilding the initrd and was able to successfully boot.
It seems like a yum update of the plymouth package wasn't sufficient to fix whatever the problem was, but uninstalling the package(s) completely and then reinstalling was.
Interesting. There may be something wonky going on there.
I've cloned this bug as bug 461641 to track that issue separately.
*** Bug 462475 has been marked as a duplicate of this bug. ***
So I pushed a plymouth build plymouth-0.6.0-0.2008.10.08.1.fc10 a few minutes ago that has been confirmed to fix things for Yanko.
It hasn't been tested in set ups with encrypted devices yet, so that may still need some work.
Leaving open until I get a test envrionment set up for that.
This got tested by jlaska and it seems to work (sans a mkinitrd bug)
*** Bug 470569 has been marked as a duplicate of this bug. ***