[MSI P35 Neo] Ubuntu 13.04 kernel panic on reboot

[ryou ezoe]

After upgraded to Ubuntu 13.04.
Rebooting cause kernel panic on boot.

Shutdown and then boot works fine.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ezoe 4109 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=b825a71e-0551-4473-a909-8f0a564777b7
InstallationDate: Installed on 2012-03-23 (399 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IwConfig:
 ppp0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: ThirdWave Corporation Prime Series
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=4048d4bb-3291-4b4b-a58e-b46b3a8e2af5 ro quiet splash
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:

Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-04-25 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 08/09/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7360
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd08/09/2007:svnThirdWaveCorporation:pnPrimeSeries:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7360:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: Prime Series
dmi.product.version: 1.0
dmi.sys.vendor: ThirdWave Corporation

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1173498

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[ryou ezoe (boostcpp)]

apport information

[JasonL (jluedke42)]

I have the same problem that started with the first restart after the Software Updater finished updating from 12.10 to 13.04. Early in the boot process, you get a stack trace that contains the text "Fixing recursive fault but reboot is necessary!"

Up until now, a full shutdown would allow it to boot without incident. But the stack trace has started happening intermittantly when powering on. This is on an AMD Athlon II X2 and Ubuntu is the only OS installed.

[Cesare Falco (c.falco)]

I randomly have the same issue, usually solved by a warm reboot, seldom needed twice.

Ubuntu is the only OS on my box (AMD X2), undergone multiple upgrades starting with 8.10.

[faical117 (faical117)]

randomly in my fresh install of ubuntu 13.04

[James Pearce (pearce-jj)]

I see this on both physical install (i5-3210M CPU) and virtual machines via KVM. Never had the issue with 12.10.

[James Pearce (pearce-jj)]

More info - seems to affect about 1 in 20 starts. Faulting boot (13.04 VM on KVM, guest is 3.8.0-21-generic using VGA adapter, host is same kernel).

Begin: Running /scripts/init-bottom ... done.
[ 0.891922] Adding 2095100k swap on /dev/vda5. Priority:-1 extents:1 across:2095100k
[ 1.144944] init: log.c:813: Assertion failed in log_clear_unflushed: ! log->io
[ 1.155410] init: Caught abort, core dumped
[ 1.158829] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000600
[ 1.158829]

Hope that helps.

[Launchpad Janitor (janitor)]

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

[Richard Huang (huangyunsong)]

I have the exact problem in ubuntu 13.04, exactly same to James Pearce's.

[Richard Huang (huangyunsong)]

My host machine is ubuntu 12.04.2 64bit, and the guest is ubuntu 13.04 64bit.

[penalvch (penalvch)]

ryou ezoe, could you please capture the oops following https://wiki.ubuntu.com/DebuggingSystemCrash ?

[ryou ezoe (boostcpp)]

Sorry.
I already upgraded to 13.10.
13.10 doesn't have this problem.

[penalvch (penalvch)]

ryou ezoe, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173498/comments/26 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.