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

Bug #554344 reported by nlind
56
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

sorry i cannot describe the problem the crash reported - it became apparent after installing mediabuntu. I was getting Mediabuntu (plymouth etc.) install update errors with just normal updates, a lot of them these past few days..

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-19-generic-pae 2.6.32-19.28
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic-pae 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic-pae i686
NonfreeKernelModules: nvidia
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
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nhl 1362 F.... pulseaudio
 /dev/snd/pcmC0D0p: nhl 1362 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH5'/'Intel ICH5 with AD1985 at irq 17'
   Mixer name : 'Analog Devices AD1985'
   Components : 'AC97a:41445375'
   Controls : 50
   Simple ctrls : 35
Date: Fri Apr 2 18:32:32 2010
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=UUID=61849c2d-90e7-43da-bd3e-d1f332406fa4
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic-pae root=UUID=d989baba-8068-4343-8849-6623afa5c311 ro quiet splash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
 1: hci0: Bluetooth
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x89/0x90()
dmi.bios.date: 10/14/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1019.005
dmi.board.name: P4P800
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1019.005:bd10/14/2004:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
nlind (nlzx319g) wrote :
Revision history for this message
E Hillman (8-launchpad-walkingdead-net) wrote :

Getting the exact same error but not on mediabuntu. This is on an Asus 1201N netbook I just upgraded from 9.10 to 10.4 - was not having this issue on 9.10!

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

Hi nlind,

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.404 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
Revision history for this message
abigsky (abigsky) wrote :

I'm getting the same bug on a HP Pavilion Elite m9250f. I'm running Ubuntu Server 10.4 with the ubuntu-desktop loaded. My installation was from scratch.

I did not notice the time it took to come out of suspend mode; I hit the button and was interrupted by my neighbor. As lovely as Ubuntu is, she easily won my attention. Hey, a guy has to have his priorities :-)

- Abigsky

Revision history for this message
Jingo (mudler) wrote :

I get this behaviour with a Thinkpad T43 too with radeon x300. I'm using the 2.6.32-21-generic kernel which came out yesterday/today. I've resumed/suspended before but have not noticed this before, so it may be a regression.

There are already 4 bug reports which point to similar behaviour. Didn't want to clutter up launchpad with another similar bug report even though my hardware is a tad different, so I attached to this one. If someone thinks I should file a separate bug report, I will try and do that next time it happens.

Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

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

tags: added: latest-bios-1019
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.