8.04 fails to boot with kernel 2.6.24-15 or 2.6.24-16

Bug #218820 reported by Patrick Dempster on 2008-04-17
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

I've been running 8.04 beta for a while now, with kernel 2.6.22-14 the system boots and runs just fine. However, with the recent updates to the kernel 2.6.24-15 and then to 2.6.24-16 the system fails to boot and "hangs" at the "loading" screen with the blue progress bar just moving back and forward. In the trimmed menu.lst only the last option boots.

patrickd@ubuntu:/media$ lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04

===File:/boot/grub/menu.lst===
title Ubuntu 8.04, kernel 2.6.24-16-generic
root (hd0,5)
kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=761e8f2c-dd8d-4042-a5bb-2ead0c26c54e ro quiet splash
initrd /boot/initrd.img-2.6.24-16-generic
quiet

title Ubuntu 8.04, kernel 2.6.24-15-generic
root (hd0,5)
kernel /boot/vmlinuz-2.6.24-15-generic root=UUID=761e8f2c-dd8d-4042-a5bb-2ead0c26c54e ro quiet splash
initrd /boot/initrd.img-2.6.24-15-generic
quiet

title Ubuntu 8.04, kernel 2.6.22-14-generic
root (hd0,5)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=761e8f2c-dd8d-4042-a5bb-2ead0c26c54e ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet

description: updated
TenLeftFingers (tenleftfingers) wrote :

Thanks for your bug report and for your contribution to ubuntu. In order to determine if this issue is usplash related, would you boot your computer with usplash disabled and then shutdown to see if you can reproduce the issue? To disable usplash for one boot time, you can follow these steps :

1.Press Esc during Grub boot delay to access the boot menu.
2.Select your actual Ubuntu boot line and press "e" to edit it.
3.Select the "kernel" line and press "e" to edit it.
4.At the end of the line, remove "splash" and "quiet" and press "enter".
5.Type "b" to boot the custom boot line.

Hi Jarlath, Thanks for taking the time to respond to this report its must appreciated. Following your suggestions I rebooted now I get the following error:

ALERT! /dev/disk/by-uuid/761e8f2c-dd8d-4042-a5bb-2ead0c26c54e does not exist. Dropping to shell.

After checking in /dev/disk/by-uuid for the link it appears that none of the linux partitions are listed.

When I rebooted to the 2.6.22 kernel the following partitions are listed.

patrickd@ubuntu:/media$ sudo blkid
[sudo] password for patrickd:
/dev/sda1: UUID="905C867A5C865B3C" TYPE="ntfs"
/dev/sda2: UUID="dd6323a0-d0b6-4fed-bf05-c7178bab69b2" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: TYPE="swap" UUID="403997d4-4fa2-45e2-8332-8d21cb971a8c"
/dev/sda5: UUID="4d09e3da-b74a-4398-b226-d8c10df2bacd" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: UUID="761e8f2c-dd8d-4042-a5bb-2ead0c26c54e" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: UUID="4E3030153030068D" LABEL="New Volume" TYPE="ntfs"
/dev/sdb1: SEC_TYPE="msdos" LABEL="ZMate 2GB" UUID="46D2-3B6A" TYPE="vfat"
/dev/sdc1: LABEL="My Book" UUID="F749-9A0F" TYPE="vfat"

TenLeftFingers (tenleftfingers) wrote :

Hi Patrick,

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies

Thanks in advance!

Jarlath

Changed in linux:
assignee: nobody → jarlathreidy

Hi Jarlath,

Here is the information you requested, should you need anything else feel free to ask.

patrickd@ubuntu:~$ uname -a
Linux ubuntu 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

and lspci-vvnn.log as I couldn't file an option to attach more than one file to the last update.

Hi Patrick,

Can you also attach your /etc/fstab . Thanks.

Hi Leann,

fstab attached as requested.

P.

Tomas 'tt' Krag (tt) wrote :

I can confirm this bug, on my Intel Mac Mini, I get the exact same error. Unfortunately after the latest update, the 2.6.22 kernel fell off the bottom of my grub menu, and I can no longer boot the computer at all.

I had to boot off the CD, go into rescue mode, and add more kernel options to grub, just to get the 2.6.22 kernel option back.

Anything newer than that, and the system fails to boot.

$ uname -a
Linux tkragMac 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

Tomas 'tt' Krag (tt) wrote :

And dmesg output

Marking as confirmed.

Changed in linux:
status: New → Confirmed
Changed in linux:
assignee: jarlathreidy → nobody

As an update to the this bug, I've since found a workaround. The workaround enabled my system to boot with the 2.4.26-16-generic kernel.

patrickd@ubuntu:~$ uname -a
Linux ubuntu 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

The workaround for me was to add "pci=nomsi" to the kernel boot options, so the entry in fstab now looks like;

kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=761e8f2c-dd8d-4042-a5bb-2ead0c26c54e ro quiet pci=nomsi splash

Tomas 'tt' Krag (tt) wrote :

adding pci=nomsi has no effect on my Intel-based macMini.
I still cannot boot with a 2.6.24 kernel

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.

Ralph Janke (txwikinger) wrote :

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

Changed in linux:
status: Confirmed → Incomplete

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers