Kernel crash on startup

Bug #94718 reported by Nicolas DERIVE
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.20-12-generic

When I try to launch the 2.6.20-12-generic kernel, it halts on "uniform CD driver" or in "Waiting for root file system" when usplash is enabled. After a few minutes, a busybox session is displayed. I think it's a regression because the 2.6.20-11-generic kernel is working.

Revision history for this message
Ben Collins (ben-collins) wrote :

This bug is fixed in 2.6.20-12.20

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

I've installed this kernel this morning, but I saw no difference with the precedent version... The same problem remains for me...Sorry...

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Thank you Nicolas for your response. I will reopen this bug.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Edit the boot command during startup and remove 'quiet splash'. If you can, take a picture of the monitor at the point that the boot process stops and attach it to this bug report. Otherwise you'll have to copy the information displayed by hand.

Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Paul Sladen (sladen) wrote :

An even easier way to do this is to select '(recovery mode)', then please can you take a digital photo of the information (stacktrace) just before the busybox prompt.

Revision history for this message
sardion (ubuntu-sardion) wrote :

I also still have this problem. Using 2.6.20-13 and nothing.
I will post the lines before the hang as soon as I can get them photoed.

Revision history for this message
sardion (ubuntu-sardion) wrote :

Attached is a photo of the screen where it hangs. Not sure how useful it will be, it detects all the devices and then just stops.

I am fairly competent with kernel stuff, let me know what else you need or if there's anything i should try. No problem compiling my own kernel etc.

Revision history for this message
sardion (ubuntu-sardion) wrote :

ps. if there are two of us still with this issue, there are more. releasing a kernel this broken in feisty would be bad. i would upgrade the importance.

Revision history for this message
sardion (ubuntu-sardion) wrote :

I've solved the issue.

My drive used to be hda and now its sda. Don't know (or need to know) why its now SCSI.

For me at least, the problem was not letting the stock /usr/sbin/update-grub script run (I use my own). The shipped one successfully changes everything to root=/dev/sda6

This should probably be mentioned in the release notes for feisty somewhere, as anyone who does not run update-grub will hit this problem (if their machine is like mine).

But the bug can be closed.

Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: timg-tpi → ubuntu-kernel-team
importance: Medium → Undecided
status: Needs Info → Rejected
Revision history for this message
Nicolas DERIVE (kalon33) wrote :
Revision history for this message
Nicolas DERIVE (kalon33) wrote :
Revision history for this message
Nicolas DERIVE (kalon33) wrote :

Seems to be OK if I replace "/dev/hda3" by "/dev/sda3" but when I restarted, I got nothing with usplash, and when I disabled it, I got "resume : could not stat the resume device file; Press Enter to boot the system". Trying to press "Enter" on normal boot with usplash gives nothing.

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

The main problem : all partitions on an IDE hard drive are recognised as sd* ones.
Other problem : with resume, but I don't know what it is.

Revision history for this message
sardion (ubuntu-sardion) wrote :

Nicolas:

In your /boot/grub/menu.lst you most likely have a resume=/dev/hdaX in the kernel options. Change that also to sda. Also check your /etc/fstab for /dev/hdaX entries.

Or try this:

Make a backup of your /boot/grub/menu.lst file
and then run

sudo /usr/bin/update-grub

That should fix the problem.

If not, let me know via email since I think this is no longer a bug of ubuntu but more of your and my setups being nonstandard (and mine is fixed by the sda thing).

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

It works, but I can't hibernate my computer... :/

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.