2.6.22-14 stock kernel hangs at boot time. But 2.6.20-15 doesn't!

Bug #158775 reported by Subharo Bhikkhu
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Please see submission ID 7dfd98bcd1ece98862ea33460bff5333 in the Ubuntu Device database. I've just upgraded to Gutsy Gibbon.

Note: The problem is in one of these linux 2.6.22-related packages, I'm not sure which, but these are the ones I have installed:
~$ dpkg -l|grep 2.6.22
ii linux-generic 2.6.22.14.21 Complete Generic Linux kernel
ii linux-headers-2.6.22-14 2.6.22-14.46 Header files related to Linux kernel version
ii linux-headers-2.6.22-14-generic 2.6.22-14.46 Linux kernel headers for version 2.6.22 on x
ii linux-headers-generic 2.6.22.14.21 Generic Linux kernel headers
ii linux-image-2.6.22-14-generic 2.6.22-14.46 Linux kernel image for version 2.6.22 on x86
ii linux-image-generic 2.6.22.14.21 Generic Linux kernel image
ii linux-restricted-modules-2.6.22-14-generic 2.6.22.4-14.9 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-restricted-modules-common 2.6.22.4-14.9 Non-free Linux 2.6.22 modules helper script
ii linux-restricted-modules-generic 2.6.22.14.21 Restricted Linux modules for generic kernels
ii linux-ubuntu-modules-2.6.22-14-generic 2.6.22-14.37 Ubuntu supplied Linux modules for version 2.

The problem is that the stock kernels I received with both with Feisty Fawn (2.6.20-16) and Gutsy Gibbon (2.6.22-14) both cause a system hang at boot time. But the stock kernel I received with even earlier, 2.6.20-15, does not have this problem. So as a workaround I've been booting with 2.6.20-15 (which is thankfully still listed in my Grub menu). This workaround sufficed when I was using Feisty Fawn, but it will no longer do: some of the new features in Gutsy Gibbon expect the 2.6.22 kernel to be there (eg. whenever plugging in any USB flash drive, in Gutsy Gibbon, while using the 2.6.20-15 kernel, it gives a mounting error, see the attachment cant_mount.png)

When I successfully boot in Gutsy Gibbon with 2.6.20-15, here are all the boot-time-related messages seen in syslog: see attachment succesful-2.6.20-15.txt

Now, compare this with a screenshot (2-6-22_freezes.jpg) of what's seen when I boot with 2.6.22-14. This screenshot shows you what is seen at the time of the hang. Note: all USB devices were disconnected at boot time when this screenshot was taken. If I have my USB mouse plugged in, then a few more USB-related messages will appear below what's seen in this screenshot at the time of the freeze. Which might mistakenly lead one to conclude the freeze is caused by some USB device that's plugged in. That is to say, I purposely disconnected all USB devices so that they would not get blamed for this freeze, which occurred without them.

Revision history for this message
Subharo Bhikkhu (subharo) wrote :
Revision history for this message
Subharo Bhikkhu (subharo) wrote :
Revision history for this message
Subharo Bhikkhu (subharo) wrote :
Revision history for this message
Mario Young (mayeco) wrote :

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 [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-source-2.6.22.

Revision history for this message
Subharo Bhikkhu (subharo) wrote :

Hi, I've managed to compile for myself a custom kernel (2.6.23.1, from source) which worked where the stock kernel 2.6.22-14 would not. How did I do it? I copied the latest stock kernel's config file (/boot/config-2.6.22-14-generic), and used it as I configured my custom kernel (/usr/local/src/linux-2.6.23.1/.config). The only options I changed were these (in the "Processor Type and Features" section):
-set the processor type to nicely match what I actually have in my box: a Pentium-4 Celeron. (which to me is not suspicious as actually solving this problem)
-turned off Symmetric Multiprocessing, as I have a single CPU. (which to me is not suspicious as actually solving this problem)
-Disabled the experimental support for "Paravirtualization support" (which to me is highly suspicious as actually solving this problem)

Then I did all the normal steps to compile, install and use my new kernel.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Dustin,

Thanks for the update. I just wanted to let you know that the upcoming Hardy kernel will hopefully resolve the issue you are seeing as it will be sync'd against the 2.6.23 mainline kernel (or newer). It should be coming out soon. If you wouldn't mind, would you be willing to test with the Hardy kernel once it does come out and let us know if it fixes this bug?

Regarding the current 2.6.22-14 kernel, the output of the hang in the digital photo doesn't seem to reveal much. Do you notice any sort of error messages that might have scrolled off the screen, or does anything show up after you let it sit for a while?

Thanks.

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This bug report is being closed because we received no reponse to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please note, the Hardy Heron Alpha4 series was recently released which contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD rather than needing to manually install. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

Changed in linux:
status: Incomplete → Invalid
Changed in linux-source-2.6.22:
status: Incomplete → Won't Fix
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.