BUG: soft lockup - CPU#1 stuck for 61s! [firefox:22662]

[David Huggins-Daines]

This just started happening after the upgrade to kernel 2.6.31-11. It has happened three times so far today, the last one was when I was away from the computer - I came back to find it locked up. Since one CPU is still okay, it doesn't lock up hard, but as soon as I try to run something it hangs.

I'm not sure if this is a duplicate with other soft lockup bugs because some of them are quite old. This literally just started happening yesterday.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dhuggins 2206 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8237'/'VIA 8237 with ALC655 at 0xc400, irq 22'
   Mixer name : 'Realtek ALC655 rev 0'
   Components : 'AC97a:414c4760'
   Controls : 49
   Simple ctrls : 34
Card1.Amixer.info:
 Card hw:1 'default'/'Generic USB Audio Device at usb-0000:00:10.3-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB0d8c:000e'
   Controls : 7
   Simple ctrls : 3
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 /var/log/dmesg -'] failed with exit code 1: [ 51.605013] eth0: no IPv6 routers present
 comm: file 2 is not in sorted order
 [ 107.221032] Clocksource tsc unstable (delta = -202860901 ns)
Date: Wed Sep 30 19:43:38 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=19f22030-4d8d-4c0e-8571-1b9311d02dfd
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: ECS K8T890-A
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-11-generic 2.6.31-11.36
ProcCmdLine: root=UUID=e42bed01-e062-455f-ba82-90e1e81a8fb2 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-11-generic N/A
 linux-firmware 1.19
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: BUG: soft lockup - CPU#1 stuck for 61s! [firefox:22662]
Uname: Linux 2.6.31-11-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 09/28/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080011
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: K8T890-A
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080011:bd09/28/2005:svnECS:pnK8T890-A:pvr1.0:rvnECS:rnK8T890-A:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.name: K8T890-A
dmi.product.version: 1.0
dmi.sys.vendor: ECS

[David Huggins-Daines (dhuggins)]

Knock on wood... haven't experienced this since upgrading to the Lucid kernel (2.6.32-10).

[Jeremy Foshee (jeremyfoshee)]

Hi David,

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? 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 from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 439752

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.

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

[David Huggins-Daines (dhuggins)]

Hi Jeremy - I believe there is a hardware bug in my motherboard or memory. Setting the DRAM clock to 166MHz has so far cured my random hangs and crashes including this one. I will mark this bug invalid as it doesn't seem to be reproducible.

[Jeremy Foshee (jeremyfoshee)]

Hi David,
     Thanks for following up on this. I am glad that you were able to determine a workaround for the problem.

Thanks!

~JFo