Kernel panic on Jetway J7F4 since upgrading to Jaunty

[Andrew Bayliss]

I upgraded my home gateway server (running Ubuntu server) from Intrepid to Jaunty yesterday using do-release-upgrade, and got a kernel panic on reboot. Sometimes Alt+SysRq will work for a bit, sometimes it doesn't, eventually it locks up completely, with the Caps Lock and Num Lock lights on the keyboard blinking. I eventually managed to get it to boot again using acpi=off. Nothing about the kernel panic seems to be logged anywhere (I guess it's happening before any filesystems are mounted), so if anyone can tell me how to force the kernel to log something I'd be happy to give it a go.
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
CurrentDmesg:

DistroRelease: Ubuntu 10.04
Package: linux (not installed)
PciMultimedia:

ProcCmdLine: root=UUID=5c69a881-5b04-4832-8e65-1b55dd2a4ed5 ro acpi=off hpet=force
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: Yes
Reproducible: Yes
Tags: lucid regression-release needs-upstream-testing
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video www-data
dmi.bios.date: 11/30/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: CN700-8237
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/30/2007:svn:pn:pvr:rvn:rnCN700-8237:rvr:cvn:ct3:cvr:

[Andrew Bayliss (abayliss)]

The kernel that doesn't boot is 2.6.28-11.42, the previous kernel from Intrepid (which is left over from the upgrade) is 2.6.27-11.31, and still boots with ACPI enabled.

[Andrew Bayliss (abayliss)]

Can anyone help me with this? I realise there's not a huge amount of information here, but I'm more than willing to experiment and gather more, I just don't know where to start!

[Andrew Bayliss (abayliss)]

I'd just like to add that this is still happening after upgrading to Karmic (kernel 2.6.31-19-generic). Can anyone give me any pointers on how to gather more information? I'm attaching a couple of photos of the errors displayed on the console, although it seems to be a different error every time.

[Andrew Bayliss (abayliss)]

Another example.

[Andrew Bayliss (abayliss)]

I found https://wiki.ubuntu.com/DebuggingACPI and have tried the various acpi options on there, here are my results:

acpi=off fine
acpi=ht fine
pci=noacpi crash
acpi=noirq crash
pnpacpi=off crash
noapic crash
nolapic crash

pci=noacpi pnpacpi=off crash
pci=noacpi noapic crash
pci=noacpi nolapic crash (but alt-sysrq works)
pci=noacpi noapic nolapic crash
noapic nolapic crash (but alt-sysrq works)

pci=noacpi pnpacpi=off noapic crash
pci=noacpi pnpacpi=off nolapic crash
pci=noacpi pnpacpi=off noapic nolapic crash (but alt-sysrq works)

[Jeremy Foshee (jeremyfoshee)]

Hi Andrew,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 371645

Also, if you could 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.]

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

apport information

[Andrew Bayliss (abayliss)]

I can confirm that this problem still occurs with linux-image-2.6.34-020634-generic_2.6.34-020634_i386.deb from the mainline builds.

[Andrew Bayliss (abayliss)]

Still happening with maverick, kernel 2.6.35-22

[Andrew Bayliss (abayliss)]

Was still happening in 11.04, and still happens in 11.10.

[Andrew Bayliss (abayliss)]

Still broken in 12.04.

[penalvch (penalvch)]

Andrew Bayliss, This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]