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

Bug #543556 reported by Daniele Cruciani
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

not sure if duplicate, here 12.xxx secs

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: daniele 2225 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xc0000000 irq 18'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,10250000,00100002 HDA:14f12bfa,10250093,00090000'
   Controls : 25
   Simple ctrls : 15
Date: Sun Mar 21 17:47:41 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=4dda44f8-4af3-48ee-a792-83453ef293e5
Lsusb:
 Bus 002 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 0402:5602 ALi Corp. Video Camera Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 9300
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=793246ac-c5ff-421b-a508-052d57cca90c ro rootfstype=ext4 quiet splash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
SourcePackage: linux
TestedUpstream: Yes
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
WpaSupplicantLog:

dmi.bios.date: 12/13/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.14
dmi.board.name: Myallm
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.14:bd12/13/2006:svnAcer:pnAspire9300:pvr0100:rvnAcer:rnMyallm:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 9300
dmi.product.version: 0100
dmi.sys.vendor: Acer

Revision history for this message
Daniele Cruciani (daniele-smartango) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Daniele,

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 12.350 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
summary: - WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
+ [RESUME 12.350s] WARNING: at
+ /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

[ 9778.180126] PM: resume of drv:button dev:PNP0C0D:00 complete after 116.853 msecs
[ 9784.960211] PM: resume of drv:battery dev:PNP0C0A:00 complete after 6780.002 msecs
[ 9785.160164] PM: resume of drv:thermal dev:LNXTHERM:01 complete after 159.887 msecs
[ 9787.360054] PM: resume of drv:nouveau dev:0000:00:05.0 complete after 2159.841 msecs
[ 9787.740107] PM: resume of drv:HDA Intel dev:0000:00:10.1 complete after 348.151 msecs
[ 9788.270619] PM: resume of drv:forcedeth dev:0000:00:14.0 complete after 530.505 msecs
[ 9788.460058] PM: resume of drv:yenta_cardbus dev:0000:04:06.0 complete after 149.983 msecs
[ 9788.740058] PM: resume of drv:usb dev:usb1 complete after 279.339 msecs
[ 9788.980058] PM: resume of drv:usb dev:usb2 complete after 239.977 msecs
[ 9789.277218] PM: resume of drv:usb dev:1-6 complete after 276.550 msecs
[ 9789.975081] PM: resume of drv:usb dev:2-2 complete after 697.820 msecs
[ 9790.100107] PM: resume of drv:acer-wmi dev:acer-wmi complete after 124.913 msecs
[ 9790.230464] PM: resume of drv:rfkill dev:rfkill0 complete after 130.346 msecs
[ 9790.230654] PM: resume of devices complete after 12167.418 msecs

tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Daniele Cruciani, 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, as per http://us.acer.com/ac/en/US/content/drivers an update is available for your BIOS (1.20). If you update to this, does it change anything?

As well, once complete, please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Also, 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

tags: added: bios-outdated-1.20 needs-upstream-testing
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.

Other bug subscribers

Remote bug watches

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