BUG: soft lockup - CPU#2 stuck for 0s! (during suspend/resume)

[Vince]

Running Lucid Alpha 3, updated March 1, 2.6.32 kernel

Suspend works, except when I resume from suspend I receive a crash report saying "your system encountered a serious kernel problem". I haven't found any symptoms yet. This happens consistently on resume from suspend.

I'm new to reporting bugs, so please let me know if there is any information I am missing.

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vince 1589 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 17'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:14f15069,17aa214c,00100301 HDA:80862804,17aa21b5,00100000'
   Controls : 10
   Simple ctrls : 5
Date: Mon Mar 1 21:03:21 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=a865f881-50d6-4f12-af64-a3c026eee1ae
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
MachineType: LENOVO 2516CTO
Package: linux-image-2.6.32-14-generic 2.6.32-14.20
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=UUID=b1bbdc50-7896-4242-afde-d1d1ca0f8244 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.31
Reproducible: Yes
SourcePackage: linux
TestedUpstream: No
Title: [1266874884.727449] BUG: soft lockup - CPU#2 stuck for 0s! [firefox-bin:1751]
Uname: Linux 2.6.32-14-generic i686
dmi.bios.date: 01/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET49WW (1.09 )
dmi.board.name: 2516CTO
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:bvr6IET49WW(1.09):bd01/07/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2516CTO
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

[Colin Ian King (colin-king)]

Looking at the kernel log time stamp, it's incredibly large: 1266874884.727449, which suggests that you are suffering from a bug in the Time Stamp Counter (TSC) (see http://en.wikipedia.org/wiki/Time_Stamp_Counter).

This is very similar to a known issue with other Intel processors, where the top 32 bits of the 64 bit TSC gets set to 0xffffffff after coming out of resume. This causes the soft lockup code to get confused because of an overflow error and this it then it erroneously reports softlockups on various CPUs.

This error message is essentially a false positive. A workaround to stop the kernel getting confused when the TSC warps so badly when coming out of resume is to use the following kernel boot parameter: notsc

This will disable the use of the TSC. Please try this and let me know if it resolves the issue. Thanks!

[Vince (vince-romanin)]

This fixed it for me. I edited /etc/default/grub and added the notsc option after GRUB_CMDLINE_LINUX_DEFAULT=

I then ran update-grub and restarted. Since then, I have not gotten this error.

Thanks!
-Vince

[Chase Douglas (chasedouglas)]

This same issue can be seen by a WARNING bug at /build/buildd/linux-2.6.32/kernel/trace/ring_buffer.c:1984 rb_add_time_stamp.

Note that it seems that it is safe to ignore the warnings and oops messages, but it also seems safe to boot the kernel with the notsc to disable usage of the faulting TSC register. If anyone sees any adverse affects through either approach, please post your experiences here so we can further decide a best course of action.