Public bug reported:

Binary package hint: usplash

On a specific type of computer, while booting, a routine check of the
root filesystem started and almost immediately the screen turned black
and entered a power-saving mode.  If left alone for some more time (1
minute or so), the computer stops responding: pressing NumLk or CapsLk
won't toggle the LEDs, Alt-SysRq comands do nothing, and even pressing
the soft-off button does nothing.  This is critical because the next
boot (after switching off then on) will force a fsck again with the same
result.

While the screen is blank, if I switch to text console (e.g. with
Alt-F8) soon enough, I can see the fsck and the boot process completing
normally.

Removing the splash boot option also allows a clean boot.  This is a
valid workaround.

On a normal boot, whithout filesystem checks, usplash runs normally.

The problem is repeatable: just 'touch /forcefsck' and reboot.  I tested
in 2 or 3 identical computers with the same results.

This seems to be hardware related since the exact same instalation in
different computers never showed this behavior.

Hardware summary:
ASUS P4R8L motherboard
Intel(R) Pentium(R) 4 CPU 3.00GHz
Radeon 9100 IGP

Dual boot configuration (Windows XP, Linux Ubuntu 9.04).
The root partition being checked is a typical ext3 (/dev/sda5, fstab below).

This may be related to other bugs such as:
  https://bugs.launchpad.net/ubuntu/+source/reiserfsprogs/+bug/32398
  https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/67453
  https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/49965
but none of these reported the system locking symptom.

João Rodrigues

** Affects: usplash (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Usplash turns off screen and locks the system while checking filesytem
https://bugs.launchpad.net/bugs/538697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to