Crash on boot after Gutsy upgrade. Same with LiveCD.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in module-init-tools

Went to wiki and found this

In fact, I get the very same problem while booting from CD ... Difficult for a LiveCD in a IDE drive to go on without IDE driver ...

Booting into the Gusty kernel and getting a picture of the kernel crash is important. Until then we won't know which kernel module caused the kernel to crash. It is important to get the full kernel crash, and this may have scrolled off the top of the screen. You can use Shift-PageUp to scroll backwards in the console output (and Shift-PageDown to scroll forwards again).

The output from dmesg, and lsmod on the working Feisty kernel will also be useful, as this will show what working modules are being loaded.

On the crashing Gutsy kernel, if you get a shell prompt (you don't mention it, but you should drop into a busybox shell prompt after the modprobe failure), you could try the following commands

modprobe ide_generic
exit

This may allow the system to boot up. If it does then the problem is definately due to the ide driver being loaded at bootup.

Hello !

Indeed I arrived at a BusyBox screen (at first I wasn't patient enough to get it). I took pictures (sorry for quality) of the crash (Crash 1/3 to 3/3), Tried the modprobe command, but it didn't work (you have a screenshot of the result) ... And while I was taking pictures, I issues cat /proc/modules and sent the result.

As required, I also sent the dmesg and lsmod from the older kernel.

Hope this helps !

I'm available for any comment or extra diagnosis.

Thanks for your help and regards !

Benoît

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Hello !

I trashed this machine some time ago, so I won't be able to test if the problem persists for this case ...

Sorry.

Regards,
Benoît

Thanks for the update. I'll go ahead and close this report since you no longer have access to the hardware to test. Thanks.

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.