System crashed with latest updates

Bug #904297 reported by Martin Albisetti on 2011-12-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

Twice today my system completely crashed. My current assumption is the latest updates made things more unstable, but that's just me guessing.
Screenshot of the crash: http://ubuntuone.com/6caq4MSZvStq1sYdEao2CL

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-4-generic-pae 3.2.0-4.10
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic-pae 3.2.0-rc5
Uname: Linux 3.2.0-4-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.90-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: beuno 1915 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 48'
   Mixer name : 'Silicon Image SiI1392 HDMI'
   Components : 'HDA:83847616,1028020a,00100402 HDA:10951392,1028020a,00100000'
   Controls : 32
   Simple ctrls : 19
Date: Wed Dec 14 12:00:18 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Dell Inc. XPS M1330
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic-pae root=UUID=7879f0a9-2c49-4bde-b095-b134e2626300 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-4-generic-pae N/A
 linux-backports-modules-3.2.0-4-generic-pae N/A
 linux-firmware 1.62
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2011-12-02 (12 days ago)
dmi.bios.date: 07/08/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0N6705
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd07/08/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn0N6705:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1330
dmi.sys.vendor: Dell Inc.

Martin Albisetti (beuno) wrote :
Brad Figg (brad-figg) on 2011-12-14
Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to boot into the previous kernel, and see if the crashes stop?

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Joseph Salisbury (jsalisbury) wrote :

It looks like you upgraded to Precise on December 2nd. The kernel at that time was 3.2.0-3.8. Do you still have this kernel on the system to try? If not, you can download it from:

https://launchpad.net/ubuntu/precise/i386/linux-image-3.2.0-3-generic-pae/3.2.0-3.8

Martin Albisetti (beuno) wrote :

I'll try rebooting into that kernel now, but an easy way to trigger the crash is when I run tests for my project within an lxc.
After a few runs, it'll crash the whole system.

Martin Albisetti (beuno) wrote :

Reverted to 3.0.0-12-generic-pae and no more crashes.

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.

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-5.11
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.