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

Bug #533387 reported by Timo Laine
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Every time after waking from suspend there is a warning about a serious kernel error. This has been happening for a few weeks now with all the recent two or three kernels.

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: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: VT1708B Analog [VT1708B Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: timo 1711 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe3f4000 irq 22'
   Mixer name : 'VIA VT1708B 8-Ch'
   Components : 'HDA:1106e721,104382ea,00100100'
   Controls : 34
   Simple ctrls : 18
Date: Sat Mar 6 09:15:58 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=28369c7b-b880-444c-b269-e142325d4276
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
MachineType: System manufacturer System Product Name
Package: linux-image-2.6.32-15-generic 2.6.32-15.22
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-15-generic root=UUID=904997fa-f913-4be2-a4c2-475d15276398 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.32
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  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+0x89/0x90()
Uname: Linux 2.6.32-15-generic i686
dmi.bios.date: 08/24/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5QL-CM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd08/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-CM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

Hi Timo,

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.936 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
Timo Laine (timoroso) wrote :

Hi Jeremy,

and thanks for the comment. Please let me know if there is something I can do to help resolve the issue.

Revision history for this message
Andy Whitcroft (apw) wrote :

[18266.024014] PM: resume of drv:usb dev:usb7 complete after 247.941 msecs
[18276.900330] PM: resume of drv:sd dev:0:0:0:0 complete after 10820.203 msecs
[18277.380025] PM: resume of drv:usb dev:7-2 complete after 479.668 msecs
[18277.951049] PM: resume of drv:usb dev:7-2.3 complete after 571.009 msecs
[18278.528049] PM: resume of drv:usb dev:7-2.4 complete after 576.991 msecs
[18278.528252] PM: resume of devices complete after 12934.045 msecs
[25866.316014] PM: resume of drv:usb dev:usb7 complete after 247.942 msecs
[25877.360846] PM: resume of drv:sd dev:0:0:0:0 complete after 10988.615 msecs
[25877.892025] PM: resume of drv:usb dev:7-2 complete after 531.156 msecs
[25878.463048] PM: resume of drv:usb dev:7-2.3 complete after 571.009 msecs
[25879.040049] PM: resume of drv:usb dev:7-2.4 complete after 576.991 msecs
[25879.040250] PM: resume of devices complete after 13154.051 msecs
[43625.137101] PM: resume of drv:usb dev:usb7 complete after 257.029 msecs
[43635.968623] PM: resume of drv:sd dev:0:0:0:0 complete after 10784.525 msecs
[43636.556024] PM: resume of drv:usb dev:7-2 complete after 587.374 msecs
[43637.127048] PM: resume of drv:usb dev:7-2.3 complete after 571.010 msecs
[43637.704048] PM: resume of drv:usb dev:7-2.4 complete after 576.990 msecs
[43637.704250] PM: resume of devices complete after 13006.056 msecs
[51845.873092] PM: resume of drv:usb dev:usb7 complete after 257.019 msecs
[51856.804972] PM: resume of drv:sd dev:0:0:0:0 complete after 10884.875 msecs
[51857.280024] PM: resume of drv:usb dev:7-2 complete after 475.024 msecs
[51857.851048] PM: resume of drv:usb dev:7-2.3 complete after 571.009 msecs
[51858.428049] PM: resume of drv:usb dev:7-2.4 complete after 576.991 msecs
[51858.428250] PM: resume of devices complete after 12994.052 msecs
[70973.309100] PM: resume of drv:usb dev:usb7 complete after 257.027 msecs
[70984.216087] PM: resume of drv:sd dev:0:0:0:0 complete after 10859.973 msecs
[70984.696030] PM: resume of drv:usb dev:7-2 complete after 479.915 msecs
[70985.267049] PM: resume of drv:usb dev:7-2.3 complete after 571.004 msecs
[70985.844049] PM: resume of drv:usb dev:7-2.4 complete after 576.991 msecs
[70985.844251] PM: resume of devices complete after 12974.060 msecs
[71143.209102] PM: resume of drv:usb dev:usb7 complete after 257.030 msecs
[71154.132036] PM: resume of drv:sd dev:0:0:0:0 complete after 10875.936 msecs
[71154.612024] PM: resume of drv:usb dev:7-2 complete after 479.961 msecs
[71155.183048] PM: resume of drv:usb dev:7-2.3 complete after 571.010 msecs
[71155.760049] PM: resume of drv:usb dev:7-2.4 complete after 576.991 msecs
[71155.760249] PM: resume of devices complete after 12990.057 msecs

summary: - Warning about a serious kernel problem after waking from suspend
+ [RESUME 12.936s] Warning about a serious kernel problem after waking
+ from suspend
Revision history for this message
shane (shane-animail) wrote : Re: [RESUME 12.936s] Warning about a serious kernel problem after waking from suspend

I did go to report this also and saw this so marked as affected.
Not sure if the logs were still added but looking at my own dmesg, resume averages around 2.7 seconds with this error.

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

Timo Laine, 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://www.asus.com/Motherboards/P5QLCM/#support_Download_8 an update is available for your BIOS (0901). 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-0901
Changed in linux (Ubuntu):
status: Triaged → Incomplete
summary: - [RESUME 12.936s] Warning about a serious kernel problem after waking
- from suspend
+ WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
+ suspend_test_finish+0x89/0x90()
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.