Kernel panic at boot with kernels > 3.2.0.17

[Mathieu Perona]

Kernel panic at boot with kernels 3.2.0.17 to current.

I could not find anything helpful in the logs. Tentative help : screenshot attached.

Tried with kernel 3.4.0-030400rc2. Same Panic.

WORKAROUND: Boot into 3.2.0.17.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-generic 3.2.0.22.24
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic-pae 3.0.22
Uname: Linux 3.0.0-17-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mathieu 1917 F.... pulseaudio
Date: Mon Apr 9 16:00:38 2012
HibernationDevice: RESUME=UUID=0e90266d-f2ae-4851-a96d-c0632acf28b4
MachineType: Dell Inc. Studio XPS 1340
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic-pae root=UUID=5b896e83-4d2b-4a9d-8a87-c5f5e0ec1289 ro quiet splash
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-03-14 (26 days ago)
WpaSupplicantLog:

dmi.bios.date: 05/04/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0K171D
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.asset.tag: 1234567890
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/04/2009:svnDellInc.:pnStudioXPS1340:pvrA07:rvnDellInc.:rn0K171D:rvrA07:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Studio XPS 1340
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/

[Mathieu Perona (mathieu-perona-gmail)]

Tried with kernel 3.4.0-030400rc2. Same Panic. Just to be clear : 3.2.0.17 boots fine. Problem starts with 3.2.0.18, and all kernels to date (I have tested each time a new kernel has been available in Precise).

Sorry for not being more specific. Do not hesitate to ask if you think I can find more details in some log I have overlooked.

[Mathieu Perona (mathieu-perona-gmail)]

An then, another thing that may not be apparent in apport's reports: at the first occurence, I thought that it was a problem with the video driver (I used nouveau then). I booted from a USB key to replace nouveau by proprietary nvidia drivers, to no avail. Thus, I guess both nouveau and the nvidia drivers are not the main suspects.

[Joseph Salisbury (jsalisbury)]

Hi Mathieu,

I'd like to perform a kernel bisect to identify which commit introduced this regression in 3.2.0.18. Are you available to try a few test kernels?

If so, it would be great to first test the following two upstream kernels:

v3.2.7:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.7-precise/

v3.2.8:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.8-precise/

v3.2.9
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.9-precise/

It would be great if you could test those kernels, starting with 3.2.7. There is no need to test all of the kernels if you find the first version that has the bug before testing them all.

[Mathieu Perona (mathieu-perona-gmail)]

I'll try to do that. I do not have time to go further tonight, but I can tell you that v3.2.7 works. I will attempt to try the others in a few days.

[Mathieu Perona (mathieu-perona-gmail)]

Kernel 3.2.8 boot, kernel 3.2.9 panics.

[Joseph Salisbury (jsalisbury)]

Thanks, Mathieu.

I started a bisect between 3.2.8 and 3.2.9. I'll post a test kernel shortly. There may be ~5 test kernels to test before identifying the bad commit.

The first test kernel will be up to the following commit:
4cc383ba35be70d24fb7d43dd67f15f6ec3c7ebc

[Joseph Salisbury (jsalisbury)]

I uploaded the first test kernel, which is available at:

http://people.canonical.com/~jsalisbury/lp977237/

Can you test that kernel and report back if the bug exists in it or not?

Thanks in advance.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Mathieu Perona (mathieu-perona-gmail)]

The first kernel ( linux-image-3.2.8-030208-generic-pae_3.2.8-030208.201204102100_i386.deb) boots.

[Joseph Salisbury (jsalisbury)]

I uploaded the next test kernel, which is available at:

http://people.canonical.com/~jsalisbury/lp977237/

This kernel is built up to commit:
758e4d3da5bc2a30a7618cb8f1710e096dac0e53

Can you test that kernel and report back if the bug exists in it or not?

Thanks in advance.

[Mathieu Perona (mathieu-perona-gmail)]

That last kernel boots normally.

[penalvch (penalvch)]

Marking Triaged as mainline tested.

[Albert Einstein (spideryzarc)]

linux-image-3.2.8-030208-generic-pae_3.2.8-030208.201204122142_i386.deb workedon my dell inspiron xps 1340 . But I coun't install nvidia drivers.

It's working at full resolution without nvidia drivers. When i try install by jockey I get error message, by apt-get I can complete the install but a get no nvidia and wrong resolution after reboot.

Maybe I have messed up something else.

The jockey log is attached.

[penalvch (penalvch)]

Albert Einstein, please execute the following at the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

[Albert Einstein (spideryzarc)]

Christopher M. Penalver,

I run the command "ubuntu-bug linux" but it returned that I not using official ubuntu package and the process couldn't be completed.
I rebooted on my last working kernel ( 3.0.0-17-generic-pae) and got the same message.

[penalvch (penalvch)]

Albert Einstein, you may file a new bug via https://bugs.launchpad.net/ubuntu/+source/linux/+filebug .

[Albert Einstein (spideryzarc)]

Christopher,
How i thought, I messed up. I didn't install the headers. After the headers installation i could install nvidia drivers.

[Herton R. Krzesinski (herton)]

The screenshot of the partial trace posted on first comment, points that it's likely same ite_cir issue on bug 984387, thus marking this as a duplicate. You can remove/blacklist ite_cir module or try one of the testing kernels posted on that bug, to avoid the panic. An update is scheduled to be released fixing the issue on the kernel (for Oneiric and Precise).