Panic, Attempted to kill init. ? printk+0x2d/0x2f
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-
ProcVersionSign
Uname: Linux 3.2.0-12-
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
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(
[ 46.880038] eth0: no IPv6 routers present
Date: Fri Feb 3 13:33:01 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=
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=
PATH=(custom, user)
LANG=fi_FI.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
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.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: AMILO M
dmi.product.
dmi.sys.vendor: FUJITSU SIEMENS
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: |
added: kernel-bug-exists-upstream removed: needs-upstream-testing |
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
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.