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

[Benjamin Drung]

I sent my machine to suspend and on resume this error happens. The first thing I saw once resuming was the screen full of "noise". I switched to different virtual terminals, back to tty7, and then the "noise" was gone.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-18-generic 2.6.32-18.27
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
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: skipper 1440 F.... pulseaudio
 /dev/snd/pcmC0D0p: skipper 1440 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Audigy2'/'SB Audigy 4 [SB0610] (rev.0, serial:0x10211102) at 0x1000, irq 21'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 202
   Simple ctrls : 37
Date: Thu Apr 1 16:23:16 2010
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=UUID=34cac010-fdc1-4e0b-823e-6d5e833bfc17
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-18-generic root=UUID=084f66b9-41ed-4f11-968c-083da82522ce ro quiet splash
RelatedPackageVersions: linux-firmware 1.33
RfKill:

SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90()
dmi.bios.date: 07/15/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG33TL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD89517-802
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDG33TL:rvrAAD89517-802:cvn:ct3:cvr:

[Jeremy Foshee (jeremyfoshee)]

Hi Benjamin,

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 13.760 seconds. I'm setting this to traiged for further investigation. Thanks!

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

[Jeremy Foshee (jeremyfoshee)]

[63652.701928] PM: resume of drv:e1000e dev:0000:00:19.0 complete after 319.583 msecs
[63653.260022] PM: resume of drv:usb dev:usb5 complete after 269.998 msecs
[63653.530008] PM: resume of drv:usb dev:usb7 complete after 269.977 msecs
[63653.800007] PM: resume of drv:usb dev:usb8 complete after 269.994 msecs
[63663.763723] PM: resume of drv:sd dev:4:0:0:0 complete after 9903.533 msecs
[63664.113971] PM: resume of drv:usb dev:5-1 complete after 277.713 msecs
[63664.380093] PM: resume of drv:usb dev:5-2 complete after 266.095 msecs
[63664.969967] PM: resume of drv:usb dev:7-1 complete after 589.867 msecs
[63665.555964] PM: resume of drv:usb dev:7-2 complete after 585.976 msecs
[63666.136955] PM: resume of drv:usb dev:8-1 complete after 580.969 msecs
[63666.136984] PM: resume of devices complete after 13754.662 msecs

[penalvch (penalvch)]

Benjamin Drung, 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-rc3

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

[Benjamin Drung (bdrung)]

I am using Ubuntu 13.04 (raring) and don't experience this bug any more.