Kernel locks up with no feedback on initrd passoff

Bug #610124 reported by Paul Tagliamonte
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Upon install of 10.04 to my HP Mini 110, I rendered the system unbootable. Live CD came up normally, without issue, install finished with success.

Bootup is about 90% unsuccessful, 10% bootup continues as normal, and is runnable.

The laptop was running without issue on 10.04 Beta 2 for about three months.

This artifact presents it's self as a hang after GRUB passes off control to the initrd. There is no feedback, and is unresponsive to:
 * Keyboard Input
 * Off button
 * REISUB
 * Ctrl + Alt + Del

Tested with fresh wipes with the following images:
 * Ubuntu 10.04
 * Kubuntu 10.04
 * Xubuntu 10.04

Issue was very reproducible.

I have tried installing the nightly build of the -M kernel, with no success. It rendered the system about 80% usable, but the issue is still present.

Revision history for this message
Paul Tagliamonte (paultag) wrote :
Revision history for this message
Paul Tagliamonte (paultag) wrote :

Potentially related to bug #610126

Revision history for this message
Paul Tagliamonte (paultag) wrote :

Installed Ubuntu 9.10 Netbook Remix, issue not present. Tagging regression.

tags: added: regression-release
Revision history for this message
Paul Tagliamonte (paultag) wrote :

Hint:

This issue is also present with Archlinux 2010.05.

This suggests an upstream issue and not Ubuntu diversions on the kernel.

Also telling is the same exact error line:

b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

from the initrd.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.

Please run the following command which will attach necessary information:

apport-collect 610124

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):

First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul Tagliamonte (paultag) wrote :

Seeing as how I can't get the box running reliably with the effected kernel, I won't be able to apport-collect

Since the kernel error is in the initrd and does not pass it, dmesg won't be much use either, and I can't snag it from a locked initrd.

This issue presents it's self on kernels:

  2.6.32-22.36 ( L )
  2.6.32-24.38 ( L )
  2.6.32-21.32 ( L )
  2.6.35-12.17 ( M )

Revision history for this message
Paul Tagliamonte (paultag) wrote :

Debian kernel 2.6.32-5-686 is running great. Switched to squeeze, willing to test kernels against the platform.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Paul,

What happens if you modify the kernel parameters passed to remove 'quiet splash' and whatever else (though not ro)? Actually, even just adding a space to the end would sometimes cause my Mini 500 to complete booting, when it would otherwise also stop at

"b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16".

As such, this bug is possibly related to bug 558684.

Revision history for this message
Paul Tagliamonte (paultag) wrote :

Hey Mathieu,

bug #558684 has a very similar hardware profile to mine. I think they are related as well.

I've played a bit with splash vs no splash, I'll re-install 10.04 / 10.10 UNE and give it a shot.

An interesting note about bug #558684: I've tried the arch kernel, and it failed with the same symptoms. I think we can rule out Plymouth -- hopefully this can help narrow the playing field a bit.

I'll get to working on taking notes on different kernel / flags this weekend. I'll post the results here

Revision history for this message
Paul Tagliamonte (paultag) wrote :

No Issues on 10.10, tried with Netbook Edition, all seems well, and this issue is not presenting it's self. I'm going to close this fixed. If I'm wrong, please repoen the bug :)

Thanks, Kernel Team!

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Paul Tagliamonte (paultag) wrote :

For any other HP Mini 110 users -- Mine works with Kernel version:

2.6.35-22-generic

Godspeed!

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

Other bug subscribers

Bug attachments

Remote bug watches

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