Panic, Attempted to kill init. ? printk+0x2d/0x2f

Bug #926007 reported by Jani Uusitalo
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned

Bug Description

(Filing this a a separate issue as suggested by Bryce Harrington in comments of Bug #903831.)

With the -intel driver specified in xorg.conf (or without an xorg.conf so that -intel is used), booting Precise with the current 3.2.0-12 always results in a kernel panic. I'll attach a couple of shots I took of two instances (although to me the panic looks the same in both cases).

This began within the Precise cycle: with the early kernels I was able to boot fine, although Bug #903831 did come up then.

I have yet to try 3.2.0-13 which has just been released. Once package listings pick it up I'll give it a go and report back.

I'm able to boot by switching to fbdev in xorg.conf (the way I'm reporting this now).

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-12-generic-pae 3.2.0-12.21
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
Uname: Linux 3.2.0-12-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jani 1782 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with CS4299 at irq 10'
   Mixer name : 'Cirrus Logic CS4299 rev 4'
   Components : 'AC97a:43525934'
   Controls : 36
   Simple ctrls : 22
CurrentDmesg:
 [ 35.672075] intel8x0: clocking to 48000
 [ 36.816209] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
 [ 36.816216] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
 [ 36.816551] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [ 46.880038] eth0: no IPv6 routers present
Date: Fri Feb 3 13:33:01 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=80b87005-5f3a-4290-bba9-d30ef32f8151
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: FUJITSU SIEMENS AMILO M
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=fi:en_US:en
 PATH=(custom, user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic-pae root=UUID=f5b168d7-b4d0-40d8-b76a-8bda4fb90be5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-12-generic-pae N/A
 linux-backports-modules-3.2.0-12-generic-pae N/A
 linux-firmware 1.68
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2011-12-09 (55 days ago)
dmi.bios.date: 06/15/04
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R01-S0U
dmi.board.name: AMILO M
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Rev.A
dmi.chassis.type: 1
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR01-S0U:bd06/15/04:svnFUJITSUSIEMENS:pnAMILOM:pvr-1:rvnFUJITSUSIEMENS:rnAMILOM:rvrRev.A:cvnFUJITSUSIEMENS:ct1:cvrN/A:
dmi.product.name: AMILO M
dmi.product.version: -1
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-13.22)

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 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-13.22
Revision history for this message
Jani Uusitalo (uusijani) wrote :

Okay, I've tested 3.2.0-13.22 and the results are... annoyingly varied. Mostly the boots ended in a black, nonresponsive screen. On a couple of such boots, I was able to ssh in and get some logs. I'll attach them.

On one boot, there was a Trace different from the panic I reported. I'll attach a picture.

On yet another boot, the same panic was there just as in my shots above, just after "Starting CUPS" this time. I'll attach a picture of that too just for completeness' sake.

So the issue is definitely still there, either it just now manifests itself in slightly more random ways or is clouded by others. I tried -12 again too and that immediately produced the panic, so it's more consistent in that respect.

On a positive note, fbdev still Just Works.

Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-14.23)

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 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-14.23
Revision history for this message
teddy8241 (teddy8241) wrote :

this bug affect me on ubuntu 12.01 alpha2 whit fujitsu amilo li3710

Revision history for this message
Jani Uusitalo (uusijani) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-15.24)

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 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-15.24
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-16.25)

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 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-16.25
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-17.26)

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 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-17.26
Jani Uusitalo (uusijani)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-17.27)

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 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-17.27
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[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 by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc5 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc5'.

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.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/

tags: added: kernel-da-key
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Also, do you happen to know the specific Precise kernel version when this panic did not occur? That would be great to know, so we can perform a bisect.

tags: added: needs-upstream-testing
Revision history for this message
Jani Uusitalo (uusijani) wrote :

I've been waiting for an i386 build of RC5 to appear in the directory but it hasn't. Should I try RC4 instead or keep waiting until a newer i386 build appears? AMD64 isn't supported by the processor.

Unfortunately I didn't make a note of when exactly the issue began. But I can give you a timeframe: it wasn't there when I filed Bug #903831 on 2011-12-13, probably still not there on 2011-12-16 when I made comment #5 on the bug, and probably was there when I made comment #7 on that bug on 2012-01-06. (I'm being cautious with the 'probablies' because of all the overlapping issues here.)

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Yes, it would be great if you could test the rc4 kernel. There is an upstream issue that prevents the i386 build of rc5.

Revision history for this message
Jani Uusitalo (uusijani) wrote :

I tested 3.3.0-030300rc4 and couldn't verify that the panic that all the 3.2's above have is still present. Unfortunately I couldn't prove it doesn't either: with -intel, the first boot resulted in the 'low graphics mode' failsafe dialog with Traces in dmesg (I'm attaching it). All subsequent boots resulted in panics that didn't reveal a Trace, so they may or may not have been the one at hand. The panics still occurred when LDM should've launched: Visually it either just showed the last lines of boot log or that with the mouse cursor. (The what's-that-key was also blinking on the keyboard.)

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest precise kernel with RC6 disabled?

To disable RC6, do the following:
Hold down Left-Shift key to enter the Grub menu on boot
Hit 'e' to edit the kernel command line
Append i915.i915_enable_rc6=0 as a kernel boot parameter
For example: linux /boot/vmlinuz-3.2.0-17-generic <...> quiet splash vt.handoff=7 i915.i915_enable_rc6=0
Press Ctrl-x to boot

Revision history for this message
Jani Uusitalo (uusijani) wrote :

I'll upload a bunch of new screenshots for reference. They're all related to testing this so bear with me, I'll explain them further after uploading.

Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :

With persistent booting I was able to get a panic [1] showing with 3.3.0-030300rc4, and it looks the same as what the dmesg I posted in #29 [2] showed: print_bad_pte+0x187/0x1e0 is on top the Trace. Despite the numerous boots I was still unable to reproduce the initial printk+0x2d/0x2f, so it may be fixed in Main or masked by the print_bad_pte+0x187/0x1e0 (though this still is based only on two datapoints in a frustratingly random issue).

Whether RC6 is enabled or disabled doesn't seem to have bearing on this. 3.2.0-17 produces printk+0x2d/0x2f either way [3], and 3.2.0-18.28 also panics, though less consistently: I was only able to produce a sure printk+0x2d/0x2f once [4], with 3.2.0-18.28 non-pae. Mostly the errors fail to reveal themselves, and when they do, they are different from printk+0x2d/0x2f but also from each other: a couple of times a warn_slowpath_common+0x72/0xa0 (as in Bug #917668, though the hardware and pointers are different) occurred [5], and once it was a Bad page map [6] in unity-greeter.

* [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/32
* [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/29
* [3] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/33
* [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/34
* [5] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/35
* [6] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/36

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-18.28)

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 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-18.28
Jani Uusitalo (uusijani)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The v3.3-rc6 kernel was recently released. Would it be possible for you to test that kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc6-precise/

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

If the v3.3-rc6 still has the bug. It would be good to know the last kernel version that did not have this bug and the first kernel version that did have this bug. That will give us a starting point for a bisect.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jani Uusitalo (uusijani) wrote :

V3.3-rc6 still crashes, irregardless of RC6 being enabled/disabled.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Jani Uusitalo (uusijani) wrote :

I went back in Precise kernels [1] all the way back to 3.0.0-12.20. There seem to be no easy answers: now even 3.0.0-12.20 crashes with -intel.

I think this either means that the hardware's broken, or that the issue has been lurking in kernels all the way back to (at least) 3.0.0-12.20, and was only triggered by some early Precise updates (during the time window I described above). As I said, it (definitely) wasn't there when I filed Bug #903831 on 2011-12-13 (because I couldn't have gotten far enough to trigger that bug with this on the way).

I'll attach shots of current results with the early Precise kernels below just in case there's anything useful there.

I think I'll try ruling out hardware failure with Oneiric, either with the live disc (if that uses -intel) or by reinstalling.

* [1] https://launchpad.net/ubuntu/precise/+source/linux/

Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Jani Uusitalo (uusijani) wrote :

Alright, I think this is safe to rule as invalid because the cause is most likely hardware failure: Oneiric boot media now also fails to boot here despite being the one used to install this system initially. I even went so far back as installing Jaunty (didn't have anything more recent at hand, before Oneiric) and it also segfaults when X should start (though the graphical installer did work). I'll still do tests if @Joseph disagrees (and has new ideas to test), but for now I'll just settle for using fbdev (which seems to not trigger the issue).

Changed in linux (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.