WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()

Bug #460075 reported by Tor Klingberg
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This is pretty likely to be a duplicate, but I couldn't decide of which one.

It happened when resuming from suspend with an external monitor connected when I was trying my monitor detection scripts using xrandr. Something was loading the CPU 100% and the system was almost completely unresponsive.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tor 1903 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0640000 irq 22'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,17aa3bf8,00100004'
   Controls : 14
   Simple ctrls : 9
Date: Sat Oct 24 23:47:22 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=691f00d2-70a1-4519-9662-ebef3cec0b27
MachineType: LENOVO 40684XG
NonfreeKernelModules: wl
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=7f90da6d-afc7-423b-8b10-0b8a8aa1a92c ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops ubuntu-unr
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 04/29/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 14CN67WW
dmi.board.name: Kuril
dmi.board.vendor: Lenovo
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr14CN67WW:bd04/29/2009:svnLENOVO:pn40684XG:pvrLenovo:rvnLenovo:rnKuril:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: 40684XG
dmi.product.version: Lenovo
dmi.sys.vendor: LENOVO

Revision history for this message
Tor Klingberg (tor-klingberg) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Tor,

The warning reported here typically indicates that it took longer for your system to resume from suspend than expected. I believe there is a 5 sec barrier which your system likely exceeded. Typically you'll see something similar to "PM: resume devices took 8.664 seconds" in your dmesg output when this happens. I'm setting this to traiged for further investigation. Thanks!

[This is an automated message. Apologies if it has reached you inappropriately.]

tags: added: suspend-test-finish
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Tor Klingberg (tor-klingberg) wrote :

Ok, that makes sense. There are several entries around 3-4 seconds in dmesg, so it probably exceeds 5 seconds occasionally. I have a script at /etc/pm/sleep.d/11vgadetect that detects and enables an external screen on resume. Perhaps that is the culprit.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 417842, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
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.