Ubuntu
linux package

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

Bug #546715 reported by ksaksen on 2010-03-25

118

This bug affects 25 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Medium	Unassigned
Nominated for Lucid by Matej Kenda

Bug Description

getting a warning about problems with the kernel after taking my pc up from suspension

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.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ksaksen 1675 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb320000 irq 17'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30e7,00100400 HDA:11c11040,103c1378,00100200'
   Controls : 18
   Simple ctrls : 11
Date: Thu Mar 25 09:13:24 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=5102db6c-ad2d-4a48-a08d-f1a8d6fdb82b
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Hewlett-Packard HP EliteBook 8530w
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
PccardctlIdent:
Socket 0:
   product info: "RICOH", "Bay8Controller", "", ""
   manfid: 0x0000, 0x0000
   function: 254 (unknown)
PccardctlStatus:
Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=11b6dd26-3043-4f3f-bb1f-9813e267cc9b ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
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: 12/08/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.11
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.26
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530w
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard

Tags:

Revision history for this message

ksaksen (kristian-saksen) wrote on 2010-03-25:

AlsaDevices.txt Edit (459 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (59.8 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (9.1 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.1.txt Edit (141 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (59.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (382 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (32.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (907 bytes, text/plain; charset="utf-8")
OopsText.txt Edit (1.7 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (142.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (312.9 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (266.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Guiodic (Guido Iodice) (guido-iodice) wrote on 2010-03-25:

I have the same issue.

Atthached there is my dmesg.

tags:

added: i386

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-03-26:

Hi ksaksen,

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 16.790 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 16.790s] 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 on 2010-03-26:

[22894.965600] PM: resume of drv:nvidia dev:0000:01:00.0 complete after 704.768 msecs
[22895.310177] PM: resume of drv:usb dev:usb1 complete after 275.514 msecs
[22895.620046] PM: resume of drv:usb dev:usb3 complete after 269.837 msecs
[22895.890035] PM: resume of drv:usb dev:usb4 complete after 269.973 msecs
[22896.236635] PM: resume of drv:sd dev:0:0:0:0 complete after 344.981 msecs
[22896.820147] PM: resume of drv:usb dev:3-1 complete after 514.876 msecs
[22897.096100] PM: resume of drv:usb dev:4-1 complete after 275.921 msecs
[22897.210282] PM: resume of devices complete after 3102.598 msecs
[35120.144944] PM: resume of drv:nvidia dev:0000:01:00.0 complete after 704.103 msecs
[35120.490053] PM: resume of drv:usb dev:usb1 complete after 275.462 msecs
[35120.800030] PM: resume of drv:usb dev:usb3 complete after 269.966 msecs
[35121.070045] PM: resume of drv:usb dev:usb4 complete after 269.999 msecs
[35121.410547] PM: resume of drv:sd dev:0:0:0:0 complete after 338.862 msecs
[35122.000159] PM: resume of drv:usb dev:3-1 complete after 514.797 msecs
[35122.276124] PM: resume of drv:usb dev:4-1 complete after 275.924 msecs
[35122.380185] PM: resume of devices complete after 3085.256 msecs

Revision history for this message

Guiodic (Guido Iodice) (guido-iodice) wrote on 2010-03-26:

should be the bug related to this? https://bugs.launchpad.net/bugs/548626

Revision history for this message

ksaksen (kristian-saksen) wrote on 2010-03-26: Re: [Bug 546715] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90()

OK.
Have 8g ram to get back after suspension. Guess that's why.

On Mar 26, 2010 8:31 AM, "Jeremy Foshee" <email address hidden>
wrote:

Hi ksaksen,

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 16.790 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

** Changed in: linux (Ubuntu)
Importance: Undecided => Medium

** Summary changed:

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

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

https://bugs.launchpad.net/bugs/546715
You received this bug notification because you are a direct s...
Status in “linux” package in Ubuntu: Triaged

Bug description:
getting a warning about problems with the kernel after taking my pc up from
suspen...

Revision history for this message

Bellegarde (laurent-bellegarde) wrote on 2010-04-12:

A difficult wake up after hibernation on a lucid RT amd64 beta 2

Laurent
lprod.org

Revision history for this message

Gyorgyi Toth (tgyorgyi27) wrote on 2010-04-13:

Also got the warning after waking up from suspense.
AMD64,
2G RAM
Lucid B2

Revision history for this message

Wes Barnett (wes-barnett) wrote on 2010-04-16:

Got this warning today. Mouse was also frozen after coming out of suspend. Used to keyboard to restart, but it failed so I had to do a hard shutdown (the screen turned white and my scroll lock and caps lock keys just kept blinking). Lucid, AMD64

Jeremy Foshee (jeremyfoshee) on 2011-05-23

tags:

removed: regression-potential

Revision history for this message

penalvch (penalvch) wrote on 2013-05-27:

#10

ksaksen, 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://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3781682&prodTypeId=321957&prodSeriesId=3781677&swLang=13&taskId=135&swEnvOID=4060#120 an update is available for your BIOS (f.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

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/ .

apport-collect -p linux <replace-with-bug-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

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-f.20
tags:	removed: i386
Changed in linux (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-07-26:

#11

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

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

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

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package