periodic kernel crash and system reboot

Bug #593650 reported by Jamin W. Collins
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Periodically, I'll come back to my system to find it back at the login screen. Upon logging in, I will be prompted to file a bug report for a kernel crash.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jcollins 2062 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe220000 irq 17'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20bb,00100400'
   Controls : 30
   Simple ctrls : 19
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08'
   Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Mon Jun 14 06:40:09 2010
Frequency: Once every few days.
HibernationDevice: RESUME=UUID=1fbfa69c-fb52-4aee-ad35-9c523aa14974
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=30218f9a-6f90-4eab-9ba5-f54897e842cb ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
WifiSyslog:
 Jun 14 06:36:01 odin kernel: [ 646.162572] CE: hpet increasing min_delta_ns to 15000 nsec
 Jun 14 06:37:27 odin NetworkManager: <info> (wlan0): supplicant connection state: completed -> group handshake
 Jun 14 06:37:27 odin NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed
dmi.bios.date: 05/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC6WW (2.26 )
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn:pvrThinkPadT61p:rvnLENOVO:rn:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.version: ThinkPad T61p
dmi.sys.vendor: LENOVO

Revision history for this message
Jamin W. Collins (jcollins) wrote :
Revision history for this message
Jamin W. Collins (jcollins) wrote :

Hopefully this self-created retrace is of some use to someone.

Revision history for this message
Jamin W. Collins (jcollins) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Jamin,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jamin W. Collins (jcollins) wrote :

Where might I find the debug builds of the main line kernels?

Revision history for this message
Jamin W. Collins (jcollins) wrote :

While the mainline kernel does not appear to suffer the same periodic reboots as the current stable kernel version (2.6.32-22-generic), there is some odd interaction between the mainline kernel (2.6.35-020635rc3-generic) and libvirt. Attempting to start Windows XP VMs results in an infinite BSOD UNMOUNTABLE_BOOT_VOLUME loop. Starting Ubuntu VMs results in a read-only filesystem. Reverting the the stable kernel version results in normal libvirt functionality.

tags: removed: needs-upstream-testing
Revision history for this message
Jamin W. Collins (jcollins) wrote :

Should also be noted that calling kvm manually with the VM's disk image under the mainline kernel worked fine (for example: kvm -hda $vm_disk). So, it would appear that the problem lies between the new kernel and libvirt in some way.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jamin W. Collins (jcollins) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Jamin W. Collins, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please capture the oops following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Capturing_OOPs ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

description: updated
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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