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

Bug #451807 reported by Todd Bradshaw
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

probably a dupe of Bug #417842

It looks like the same problem with resume from ram different hardware tho.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: todd 30064 F.... pulseaudio
 /dev/snd/seq: timidity 2504 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x50320000 irq 22'
   Mixer name : 'SigmaTel STAC9271D'
   Components : 'HDA:83847627,80862503,00100201'
   Controls : 37
   Simple ctrls : 24
Date: Wed Oct 14 18:05:23 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=cbf76f3a-3071-4e41-b837-475dd1074751
IwConfig:
 lo no wireless extensions.

 eth2 no wireless extensions.

 vboxnet0 no wireless extensions.
Package: linux-image-2.6.31-13-generic 2.6.31-13.45
ProcCmdLine: root=UUID=19fc5e1e-bd56-4df8-8055-1bddbe44655f ro quiet
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-13-generic N/A
 linux-firmware 1.22
RfKill:

SourcePackage: linux
Tags: kernel-oops
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-13-generic i686
WpaSupplicantLog:

dmi.bios.date: 11/17/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: MQ96510J.86A.1754.2008.1117.0002
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG965OT
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD63733-205
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrMQ96510J.86A.1754.2008.1117.0002:bd11/17/2008:svn:pn:pvr:rvnIntelCorporation:rnDG965OT:rvrAAD63733-205:cvn:ct3:cvr:

Revision history for this message
Todd Bradshaw (snooptodd) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi snooptodd,

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. Based on your dmesg output I see PM: resume devices took 10.328 seconds. 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
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.