WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x89/0x90()

Bug #551167 reported by Noorez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Not sure if I can mark this specific bug as a duplicate to others but it feels very similar. This bug seems to occur when I need to restart my laptop by holding down the power button as it did not resume correctly from a suspend. Specifically, suspend/resume was done when opening and closing my laptop lid.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-17-generic-pae 2.6.32-17.26
Regression: No
Reproducible: No
TestedUpstream: No
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic-pae 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic-pae i686
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
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0c00000 irq 22'
   Mixer name : 'Realtek ALC861'
   Components : 'HDA:10ec0861,11791205,00100300 HDA:11c13026,11790001,00100700'
   Controls : 11
   Simple ctrls : 8
Card1.Amixer.info:
 Card hw:1 'Audio'/'USB Audio at usb-0000:00:1d.2-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB0c45:17cf'
   Controls : 5
   Simple ctrls : 4
CheckboxSubmission: 5c38a976b34d92c6d1a9804798209790
CheckboxSystem: f134069bba098730d27f59b402920826
Date: Mon Mar 29 13:27:59 2010
Failure: oops
Frequency: Once every few days.
HibernationDevice: RESUME=UUID=515a11bf-bf0f-4589-b94b-c490162fe857
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: TOSHIBA Satellite A100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic-pae root=UUID=bdc20507-9d68-4a3c-b8a7-b7a3e192d078 ro quiet splash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x89/0x90()
dmi.bios.date: 07/12/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: CAPELL VALLEY(NAPA) CRB
dmi.board.vendor: Intel Corporation
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/12/2007:svnTOSHIBA:pnSatelliteA100:pvrPSAA9C-SK900E:rvnIntelCorporation:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Satellite A100
dmi.product.version: PSAA9C-SK900E
dmi.sys.vendor: TOSHIBA

Revision history for this message
Noorez (noorez-kassam) wrote :
Revision history for this message
Noorez (noorez-kassam) wrote :

uname -a > uname-a.log

Revision history for this message
Noorez (noorez-kassam) wrote :

cat /proc/version_signature > version.log

Revision history for this message
Noorez (noorez-kassam) wrote :

dmesg > dmesg.log

Revision history for this message
Noorez (noorez-kassam) wrote :

sudo lspci -vnvn > lspci-vnvn.log

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Noorez,

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. A patch to prevent this warning has been applied via bug 464552. As a result I'm marking this as a duplicate to bug 464552. Please continue to track this issue at that report. Thanks!

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

tags: added: suspend-test-finish
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.