Kernel panic at boot after upgrading from 9.10 to 10.04

[lid]

I was successfully running 9.10 with 2.6.31-19-generic (amd64). However, when I upgraded to Lucid Lynx 10.04 alpha 3 (linux-image-2.6.32-15-generic), the system no longer boots with the new kernel. The relevant line seems to be:
[ 1.610000] Kernel panic - not syncing: Fatal exception in interrupt
See below for a more complete log.

I have attempted to find the problem in the upstream kernel, testing with linux-image-2.6.31-02063112-generic and linux-image-2.6.32-02063209-generic (amd64). Both of these had the same problem.

My grub.cfg looks like this:
menuentry "Ubuntu installed" {
 fakebios
 search --set -f /vmlinuz
 linux /vmlinuz video=efifb vga=normal noefi acpi=force root=/dev/sda3 console=tty0 console=ttyS0,115200n8
 initrd /initrd.img
}

I'm running this on an XServe1,1 with an efi grub2.

ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 2 2010-03-05 18:00 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.20.
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Mar 5 18:15:31 2010
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=14c4bd33-f939-469f-af5a-dbc0513b6017
IwConfig: Error: [Errno 2] No such file or directory
Package: linux-image-2.6.32-15-generic 2.6.32-15.22
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-generic video=efifb vga=normal noefi acpi=force root=/dev/sda3 console=tty0 console=ttyS0,115200n8
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
Regression: No
RelatedPackageVersions: linux-firmware 1.31
Reproducible: Yes
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.31-19-generic x86_64
WifiSyslog:
 Mar 5 17:19:13 vm1 kernel: imklog: Cannot read proc file system, 1.
 Mar 5 17:36:35 vm1 kernel: imklog: Cannot read proc file system, 1.
 Mar 5 17:49:42 vm1 kernel: imklog: Cannot read proc file system, 1.
 Mar 5 18:00:33 vm1 kernel: imklog: Cannot read proc file system, 1.

[Ike (eike-stang)]

Same Issue here after upgrading from 09.10 to 10.04 alpha 3 (with linux-image-2.6.32-15-generic as well as 2.6.33-020633-generic).

Last message seen on screen: kernel: imklog: Cannot read proc file system, 1.

[lid (lid)]

I obtained the kernel output from the serial console before it hung. Note that this is a slightly newer kernel than the one that was failing before. Let me know you need more information.
<snip>
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-16-generic (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-3ubuntu1) ) #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 (Ubuntu 2.6.32-16.25-generic)
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz video=efifb vga=normal noefi acpi=force root=/dev/sda3 console=tty0 console=ttyS0,115200n8
</snip>
<snip>
[ 1.560104] SCSI subsystem initialized
[ 1.564028] usbcore: registered new interface driver usbfs
[ 1.570014] usbcore: registered new interface driver hub
[ 1.575337] usbcore: registered new device driver usb
[ 1.580113] ACPI: WMI: Mapper loaded
[ 1.583680] PCI: Using ACPI for IRQ routing
[ 1.590674] initcall pci_subsys_init+0x0/0x70 returned with preemption imbalance
[ 1.598203] NetLabel: Initializing
[ 1.600006] BUG: unable to handle kernel paging request at 00000000c199fa40
[ 1.606988] IP: [<ffffffff81059714>] update_curr+0x124/0x1e0
[ 1.610000] PGD 0
[ 1.610000] Thread overran stack, or stack corrupted
[ 1.610000] Oops: 0000 [#1] SMP
[ 1.610000] last sysfs file:
[ 1.610000] CPU 0
[ 1.610000] Modules linked in:
[ 1.610000] Pid: 1, comm: swapper Not tainted 2.6.32-16-generic #25-Ubuntu
[ 1.610000] RIP: 0010:[<ffffffff81059714>] [<ffffffff81059714>] update_curr+0x124/0x1e0
[ 1.610000] RSP: 0018:ffff880028203e48 EFLAGS: 00010086
[ 1.610000] RAX: ffff88017bab8000 RBX: 0000000028028868 RCX: ffff88017fc18800
[ 1.610000] RDX: 0000000000018570 RSI: 0000000000000000 RDI: ffff88017bab8038
[ 1.610000] RBP: ffff880028203e78 R08: 00000000000045e7 R09: 000000000000000f
[ 1.610000] R10: 0000000000000001 R11: 0000000000000000 R12: ffff880028215b70
[ 1.610000] R13: 000000005f5e1179 R14: 0000000000988d18 R15: 0000000000015b00
[ 1.610000] FS: 0000000000000000(0000) GS:ffff880028200000(0000) knlGS:0000000000000000
[ 1.610000] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[ 1.610000] CR2: 00000000c199fa40 CR3: 0000000001001000 CR4: 00000000000006f0
[ 1.610000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1.610000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 1.610000] Process swapper (pid: 1, threadinfo ffff88017bac0000, task ffff88017bab8000)
[ 1.610000] Stack:
[ 1.610000] ffff8800282164c0 00000000000104e0 ffff88017bab8038 ffff880028215b70
[ 1.610000] <0> 0000000000000000 0000000000000000 ffff880028203ea8 ffffffff810597f7
[ 1.610000] <0> ffff880028203e98 ffff88017bab8038 0000000000000000 ffff88017bab8000
[ 1.610000] Call Trace:
[ 1.610000] <IRQ>
[ 1.610000] [<ffffffff810597f7>] entity_tick+0x27/0x140
[ 1.610000] [<ffffffff81059942>] task_tick_fair+0x32/0x50
[ 1.610000] [<ffffffff81058586>] scheduler_tick+0x116/0x290
[ 1.610000] [<ffffffff810752b2>] update_process_times+0x52/0x70
[ 1.610000] [<ffffffff8109172c>] tick_periodic+0x2c/0x90
[ 1.610000] [<fffffff...

[Goofy (gfiala)]

Have probably same issue here: it was ok with lucid-alpha1 (xubuntu), however alpha3 and the daily build from sunday 7th of march 2010 fail to boot.

Directly after loading the kernel it oopses and instantly reboots, one can not really see whats printed there (and i have no serial consola available here).

Behavior is same on 2 different PC's:
-Centrino
-Centrino Duo

Behaviour is same when:
acpi=off noapic nolapic nosmp

[bert07 (marien.bert)]

Same here. Kernel panic when trying to log in Mandriva 2010 and PCLinuxOS 2010.

Can this be (one of) the reason(s)?

A disk is in both GRUB's referred to differently.

--------------------GRUB------------GRUB2
/dev/sda1-------(hd0,0)---------(hd0,1)
/dev/sdb1-------(hd1,0)---------(hd1,1)

So, when GRUB2 passes on (let us say for sda1) (hd0,1), but once the kernel of a distro still using GRUB is loading, it expects (hd0,0)

Does this make sense?

[Jeremy Foshee (jeremyfoshee)]

Hi lid,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]