Ubuntu
linux package

[RESUME 10.990s] WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90()

Bug #534893 reported by Victor Costan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

This looks similar to another wake-up bug on 2.6.32. I'm opening it because the hardware doesn't match. Please remove if my judgement is incorrect.

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: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: victor 4154 F.... pulseaudio
 /dev/snd/pcmC0D0p: victor 4154 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xdf480000 irq 20'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,106b4000,00100103'
   Controls : 36
   Simple ctrls : 20
Date: Mon Mar 8 21:29:12 2010
DistroRelease: Ubuntu 10.04
Failure: oops
Frequency: Once a day.
HibernationDevice: RESUME=UUID=54abe5bc-a430-46c6-8516-a3cc992af6d0
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Apple Inc. MacBookPro5,1
NonfreeKernelModules: nvidia wl
Package: linux-image-2.6.32-16-generic 2.6.32-16.24
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=7d79244e-89c3-4bf4-8bfe-cebeaf61c8c0 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.32
Reproducible: No
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: No
Title: WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90()
Uname: Linux 2.6.32-16-generic x86_64
dmi.bios.date: 05/05/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP51.88Z.007E.B05.0905051508
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F42D86C8
dmi.board.vendor: Apple Inc.
dmi.board.version: Proto
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 8
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42D86C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP51.88Z.007E.B05.0905051508:bd05/05/09:svnAppleInc.:pnMacBookPro5,1:pvr1.0:rvnAppleInc.:rnMac-F42D86C8:rvrProto:cvnAppleInc.:ct8:cvrMac-F42D86C8:
dmi.product.name: MacBookPro5,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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

Hi Victor,

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.990 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
Andy Whitcroft (apw) wrote :

[ 7291.430250] PM: resume of drv:battery dev:PNP0C0A:00 complete after 9589.680 msecs
[ 7291.910107] PM: resume of drv:usb dev:usb3 complete after 109.978 msecs
[ 7292.020110] PM: resume of drv:usb dev:usb4 complete after 109.988 msecs
[ 7292.484973] PM: resume of drv:sd dev:0:0:0:0 complete after 384.451 msecs
[ 7292.676039] PM: resume of devices complete after 10993.651 msecs

summary: - WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
+ [RESUME 10.990s] WARNING: at
+ /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
summary: - [RESUME 10.990s] WARNING: at
+ [RESUME 10.990s] [RESUME 10.990s] WARNING: at
/build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
summary: - [RESUME 10.990s] [RESUME 10.990s] WARNING: at
+ [RESUME 10.990s] WARNING: at
/build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
Jeremy Foshee (jeremyfoshee)
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Victor Costan, thank you for reporting this and helping make Ubuntu better. Lucid reached EOL on May 9, 2013.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.