Multiple freeze during boot

[Patrice Vetsel]

Binary package hint: plymouth

During the boot I have a first freeze on ubuntu logo. To pass it I switch to Ctrl+Alt+F1 and come back to Alt-F7
I access gdm, enter login+ pass and got a new freeze. Make another switch to Ctrl+Alt+F1 and come back to Alt-F7 and freeze disapear and gnome is ready.

ProblemType: Bug
Architecture: i386
Date: Thu Jan 21 08:46:01 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
Package: plymouth 0.8.0~-7
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
SourcePackage: plymouth
Uname: Linux 2.6.32-11-generic i686

[shankao (shankao)]

Do you get a "mountall: cannot connect to plymouth" during boot? This can be a duplicate of bug #505584.

[Patrice Vetsel (vetsel-patrice)]

Yes I have this message, but looking at #505584 I don't have the same effects. I don't think that's the same bug, so I don't mark it duplicate, waiting for more investigations.

[shankao (shankao)]

In my case, I was able to "boot" by reinstalling the X vesa driver that apparently, was I had lost in some X upgrade in the lucid cycle. It could be a workaround for your problem also.

[Steve Langasek (vorlon)]

Patrice,

Is this reproducible for you with plymouth 0.8.0~-8?

[Jan Nekvasil (jan-nekvasil)]

I'm experiencing similar behavour with with plymouth 0.8.0~-8 (kernel 2.6.32-12-generic x86_64).

After upgrade to 0.8.0~-8, first boot (with ureadahead reprofiling) went well except for missing plymouth logo. Very next boot ended with black screen, blinking text cursor upper left corner, unmovable mouser pointer in center and „ready to log in“ sound. Changing the vts back and forth resulted in gdm visible and responsible on the screen, but selecting username led to hard lockup. No chance to change vts once more, contrary to what Patrice Vetsel described in original report.

Booting without „quiet splash“ options allowed me to login (with gdm running on tty1) without problems, but the session hard locked after few minutes everytime I tried that. For now, after "sudo apt-get purge plymouth", gdm started on tty7 and session is up and running for a while without any troubles.

Only change I made some time before upgrading plymouth which can possibly affect the whole process was "sudo dpkg-reconfigure console-setup" for setting console font to "fixed" and keyboard to "US". Booted many times with that and previous plymouth version without problems.

[vmc (vmclark)]

After todays update of Plymouth, I no longer had the logo on boot and it stopped and froze at some undetermined point. Power cycle was the only alternative.

Removing Plymouth fixed my issue.

I get the message on boot up, "..could not connect to plymouth", whether Plymouth is installed or not?!

[Patrice Vetsel (vetsel-patrice)]

@Steve : I confirm my bug with plymouth 0.8.0~-8

[Patrice Vetsel (vetsel-patrice)]

@Steve : here is syslog as there are multiples messages may be usefull at the end

[Harry (harry33)]

It would be interesting and perhaps helpful to know what graphics cards people have affecting this bug.
Also see another plymouth bug, but affecting NVidia cards:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412

[drs305 (drs305)]

I have what may be a related problem. I updated this morning and now whenever I attempt to enter something in a search box the system locks up. No keyboard or mouse inputs allowed. I rebooted into recovery mode, uninstalled plymouth, and now everything is working again.

Note: I use autologon so I did not have to enter anything to get to the Desktop.

Lucid A2, 64-bit
2.6.32-11-generic
plymouth 0.8.0~-8

[Harry (harry33)]

drs305,
that is the bug I mentioned above (516412), not this one.

[Marco Simonelli (sumydi)]

In my last update I updated grub and then plymouth didn't crash, so the problem is solved.

[mikeyphi (mikeyphi)]

No so I'm afraid...I had trouble with the latest grub-pc, having worked
around that I reinstalled Plymouth and my original problem returned -
for me it's an issue with Nvidia - the system is asking it to run my
screen with out of range parameters.

On Thu, 2010-02-04 at 18:10 +0000, Marco Simonelli wrote:
> In my last update I updated grub and then plymouth didn't crash, so the
> problem is solved.
>

[Dmitry Tantsur (divius)]

The same problem as in subj. See bug 518452.

[drs305 (drs305)]

My situation deteriorated to the same freeze during boot as described above. I get a multicolored blue boot progress indicator (?) partway across the lower part of my screen, followed by an eventual freeze which can be cleared only with a hard reboot. Removing plymouth resolves the issue each time. Reinstalling plymouth causes the problem to reoccur every time.

Situation remains though the updates on 2-7-10.

Specs same as post 11, although I think there was an update to -12 kernel. Sorry, I'm not on the problem machine.

[Steve Langasek (vorlon)]

Could those experiencing this issue please try installing the attached file in /etc/init/plymouth-splash.conf on your systems (with the plymouth package installed, of course), and report whether it makes a difference?

[Steve Langasek (vorlon)]

Erk, sorry, meant to send that to a different bug report. I don't think this is going to help the described freeze.

[Patrice Vetsel (vetsel-patrice)]

@Steve : indeed (nothing has changed with your attached file)

[Jan Nekvasil (jan-nekvasil)]

@Steve Langasek: The plymouth-splash.conf you provided fixes that freezes completely for me. Rebooted many times, everything's OK. Thanks a lot!

[Jan Nekvasil (jan-nekvasil)]

Uh-oh, not everything's so great. After unplugging my external monitor (I have Dell Latitude E5500 1440x900 LVDS + 1280x1024 LCD VGA) and reboot, the freezes are here again. I tried to plug ext. monitor back in and reboot once more, but with no luck.

[Jan Nekvasil (jan-nekvasil)]

After today's upgrade to libplymouth2 0.8.0~-9ubuntu1 I tried plymouth again. And again, with ext. monitor connected, all went well. There is a small change to better state of things with booting without ext. monitor. As previous, the boot ended with black screen with text cursor, allowing me to change vts to tty1 and back to tty7 with gdm. After login system freezes as usual, but Alt+SysRq+K is able to kill xserver and gdm will restart, allowing me to login with no problems this time.

The other interesting thing is that plymouth logo appears at boot after mounting filesystems, that means not immediately after GRUB done it's part.

[Jan Nekvasil (jan-nekvasil)]

Well, now I'm quite puzzled. I have done "sudo dpkg-reconfigure console-setup" once again, and all works perfect now (except plymouth starting late, but that's different bug). Rebooted five times, everything's OK. Strange.

[Steve Langasek (vorlon)]

plymouth starting late is not a bug. By design, it is not included in the initramfs and is only started after the root filesystem has been mounted.

[jage (jage)]

Successfully solved my problem with sudo dpkg-reconfigure console-setup.

I have ATI and on boot had to switch screens and back to CTRL+ALT+F7 to render gui, and additionally hitting the [ENTER] key would lock up the system (to the point where switching CTRL+ALT+F2 wouldn't work).

After running "sudo dpkg-reconfigure console-setup" in a terminal window, going through the prompts and rebooting the system seems back to normal.

[00raq00 (00raq00)]

I have FL90 and reconfigure console-setup doesn't work for me. Only remove plymouth works :/

[Jan Nekvasil (jan-nekvasil)]

Ater today's upgrade to kernel 2.6.32.13.13, freezes are here again, no matter how much I try with "sudo dpkg-reconfigure console-setup" (which by the way has no effect on console at boot time and must be ran manually with "sudo service console-setup start").

[00raq00 (00raq00)]

Remove works on 2.6.32.13 :)

[00raq00 (00raq00)]

0.8....10 plymouth dont resolve problem

[vmc (vmclark)]

I'm not sure if I need to open another bug report against Plymouth?

After todays latest updates, specifically Plymouth:
aptitude show libplymouth2
Package: libplymouth2
State: installed
Automatically installed: no
Version: 0.8.0~-10

I re-install plymouth and after the 4th re-boot it froze.
It freezes right after the messages init/bottom &fsck.

Not only does it freeze but my lcd monitor goes from green light to yellow,
 meaning no video signal at all!

If this is not related to this bug, let me know.

[00raq00 (00raq00)]

this bug is freeze screen after click [enter] :)

[shankao (shankao)]

@00raq00: your bug can be a duplicate of #516412.

[vmc (vmclark)]

I think I found a solution to those that, like myself, use the auto login feature.

If I removed the auto login:
"System > Administration > Login Screen" , from
Log in automatically to
show the screen for choosing who will log in

Then I no longer have a problem problem and Plymouth works without freezing.

It looks like the login automatically & Plymouth have a problem somewhere.

[filip (bandit-s-fw)]

I also get this bug. intel 945 GM.
I also see this error message: drm_mode_getfb error invalid framebuffer id.
Maybe this can help solve the problem. Is it a kernel bug?

[00raq00 (00raq00)]

I turned off automatically login and it doesn't resolved plymouth problem.

[00raq00 (00raq00)]

git clone git://anongit.freedesktop.org/plymouth

Next configure and compile it:

> cd plymouth
> ./autogen.sh --prefix=/usr/ --with-system-root-install
> make
> make install

it resolve problem :) but i'm waiting for .get from repository

[Patrice Vetsel (vetsel-patrice)]

00raq00 can you confirm this bug if so please set it's status from NEW to CONFIRMED

[Erick Brunzell (lbsolost)]

I changed status from New to Confirmed.

Nothing new to add, just that I'm effected also w/VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro].

[Patrice Vetsel (vetsel-patrice)]

Always here on 0.8.0-12

[Patrice Vetsel (vetsel-patrice)]

I attach a video of daily-iso lucid amd64 20100310
You can see that we arrive at a screen with just the background and cursor (that's what I call freeze), and blue led activity of usb key stay off forever.

Until I switch (ctrl+alt+f1), and with this switch , blue led power on and in background Xorg session continue (after the freeze), be back to Alt+F7 and we can see that ubiquity is here.

[Patrice Vetsel (vetsel-patrice)]

Do we report this bug upstream ?
Do testing latest fedora 13 alpha usefull ?

[Patrice Vetsel (vetsel-patrice)]

Can we have a new package synced from git upstream ?

[Steve Langasek (vorlon)]

This is almost certainly a symptom of the same underlying bug as bug #523788 and bug #532047, which are not fixed upstream. Scott James Remnant is in the process of fixing this, and the fixes are expected to be uploaded to lucid today.

[Patrice Vetsel (vetsel-patrice)]

@Steve : indeed, seem's that #523788 is a duplicate of my bug. But as #523788 is assigned to Scott I report my bug #510524 as a duplicate of #523788.

For information, Fedora 13 Alpha have the same bug on my netbook ;)

[Erick Brunzell (lbsolost)]

I did a fresh install on the 13th with the 03/13/10 daily build (i386) and thought things were peachy until a few hours ago. Odd I'd rebooted probably about a dozen times just fine, well I'd still get some text along with the splash, but I'd get to GDM alright and login just fine, then a few hours ago I was getting kicked to TTY again and I couldn't for the life of me get X to start.

I'd get a text login and go to a command prompt but couldn't startx no matter what I tried so I removed plymouth and did a sudo reboot and now I'm booting fine again (of course with no splash). And I've seen only a few updates that didn't appear to be related to plymouth. What could have changed after a dozen reboots I don't know.

[Scott James Remnant (Canonical) (canonical-scott)]

Erick: that sounds like bug #538214 to me, just press Alt+F7 to get to your X server

[Patrice Vetsel (vetsel-patrice)]

I'v re-opened my bug under #539507