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

Bug #523824 reported by Toby Smithe
566
This bug affects 126 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
Nominated for Lucid by Josh

Bug Description

I do not know if this is a duplicate of bug 496428 or bug 517755, but as they are both reported to occur in different locations in suspend_test_finish, and as neither of those seem to involve radeon hardware, I'm opening a new report to be on the safe side.

1. Suspend takes a very long time to resume.
2. ACPI doesn't seem to work unless I trigger its restarting by removing and inserting the power adapter. This is pretty dangerous, as on a number of occasions, the system has overheated due to the fans not starting; this isn't helped by the lack of thermal control in the current radeon driver.

Steps to reproduce:
1. Suspend the machine.
2. Try to resume.
3. Wait.
(4. Remove and re-insert power supply; `acpi -t` gives false readings of 0.0 degrees C, otherwise)

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
ArecordDevices:
 ALSA lib conf.c:3272:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
 ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL hw:0
 arecord: device_list:232: control open (0): No such file or directory
 **** List of CAPTURE Hardware Devices ****
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: toby 2172 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Error: command ['amixer', '-c', '0', 'info'] failed with exit code 1: ALSA lib conf.c:3272:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
 ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL hw:0
 amixer: Control device hw:0 open error: No such file or directory
Card0.Amixer.values:
 Error: command ['amixer', '-c', '0'] failed with exit code 1: ALSA lib conf.c:3272:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
 ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL hw:0
 amixer: Mixer attach hw:0 error: No such file or directory
Card1.Amixer.info:
 Error: command ['amixer', '-c', '1', 'info'] failed with exit code 1: ALSA lib conf.c:3272:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
 ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL hw:1
 amixer: Control device hw:1 open error: No such file or directory
Card1.Amixer.values:
 Error: command ['amixer', '-c', '1'] failed with exit code 1: ALSA lib conf.c:3272:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
 ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL hw:1
 amixer: Mixer attach hw:1 error: No such file or directory
Date: Thu Feb 18 14:16:18 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=1ba7019e-14ee-4e9f-ad54-8747f421d94f
MachineType: Dell Inc. Studio 1537
NonfreeKernelModules: wl
Package: linux-image-2.6.32-13-generic 2.6.32-13.18
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-13-generic root=UUID=f5cadb34-d259-4135-a92d-f4bad690bcfc ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.29
Reproducible: Yes
RfKill:
 1: hci0: Bluetooth
  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+0x88/0x90()
Uname: Linux 2.6.32-13-generic x86_64
dmi.bios.date: 05/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0P132H
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A09
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/27/2009:svnDellInc.:pnStudio1537:pvrA09:rvnDellInc.:rn0P132H:rvrA09:cvnDellInc.:ct8:cvrA09:
dmi.product.name: Studio 1537
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.

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

Hi Toby,

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.360 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
Toby Smithe (tsmithe) wrote :

Hmm, cool. Thanks. Is this correlated with the lack of thermal control and/or the apparent failure for acpi to restart?

Revision history for this message
Mike Basinger (mike.basinger) wrote :

Had this happen to me after rebooting from a failed resume from suspend.

Revision history for this message
Lars Kumbier (derlars) wrote :

same here, system's a Dell Studio XPS 1640

Revision history for this message
anirul (angel-calodox) wrote :

same here on a Macbook 5,1 (so without a Radeon and with a Nvidia).

Revision history for this message
Marco Ceruti (unknhawk) wrote :

i closed the laptop and opened it (compaq presario cq60-315el).
Me too have a Nvidia geforce 8200m

Revision history for this message
Mike Basinger (mike.basinger) wrote :

My laptop will now resume from suspend in kernel 2.6.32-17, but still give error message.

Revision history for this message
Eric Bennett (ebthepcguy) wrote :

this happens every day, I've been beta testing a long time but nothing this serious ever happent! about 1 minute after the problem 8 others follow and then (Kernel Panic!) plz help!
                                      -ebthepcguy- <email address hidden>

Revision history for this message
Eric Bennett (ebthepcguy) wrote :

I read the report, it seems 2 be a problem w/ the firmware not supporting a certain m-board that i'm using.
SPECS:
Acer Aspire 5532
AMD Athlon 64 TF-20 1.6 Ghz
ATI Radeon HD3200 1408 Hyper Memory
15" HD LCD
3GB Kingston DDR2
160GB HDD
Acer Nplify 802.11b/g/Draft-N
OS: Ubuntu 10.04LTS Beta 1 64 bit Desktop.
Hope the problem gets fixed soon...

THNX, Eric Bennett, (ebthepcguy).

Revision history for this message
xzero1 (kdogn) wrote :

I get this exact bug summary affter the os reports a crash and serious Kernel issue. However, the crash occurs after rebooting with no further action by me. I do have radeon hardware and suspend and resume seems to work.

Revision history for this message
Bellegarde (laurent-bellegarde) wrote :

Hi all,

I wan't in front the laptop. The screensaver start after 5 minutes, and then the computer hibernate...

When i'm came back, it get off normaly from hibernation, but after displaying the desktop, the computer freeze completly.

laurent
lprod.org

Revision history for this message
siknasa9 (randy-curry666) wrote :

Same thing but I resume and everything is fine until I reboot. Then I get the crash report.

Revision history for this message
Thomas Bousquet (tomato1090) wrote :

It happen for me too, when i wake up after a long time suspend. I mean, if i suspend and wake up the laptop 5 sec after there is no kernel error and the wake up is fast ( less than 5 sec ).

Revision history for this message
Thomas Bousquet (tomato1090) wrote :

The bug have disapeared :) Thank you.

Revision history for this message
defilerc (defilerc-gmail) wrote :

I just got this problem coming out of suspend.

Revision history for this message
Wes Barnett (wes-barnett) wrote :

The computer took a while to get out of suspend to ram, and then the mouse didn't work. I restarted, but it would not restart properly. I just remained a black screen as the scroll lock key and caps lock key flashed on in off. I did a hard shutdown, and then it started up fine with the error report.

Revision history for this message
Florian Stoll (flostoll) wrote :

Coming out of suspend works fine, but every time i get this kernel error via apport.

Revision history for this message
Manuel (manuel-schulte) wrote :

Hi Guys,

For me, same problem as for Schmankerl: resume from suspend works fine, but I also get a kernel error via apport.
I've a self assembled pc based on a Core2 duo CPU (E6750 @2.66GHz) + 2Gà of RAM and 4 HDD's using fakeraid on a MSI P35 Platinum Combo motherboard.

Aside the kernel error, the pc seem to still work fine after the resume... strange.

Keep up with the fantastic job,
Cheers,
Manuel

Revision history for this message
Manuel (manuel-schulte) wrote :

... oh yeah, I forgot to tell (it's most probably irrelevant, but): I made the upgrade from karmic to lucid via the update manager when lucid did hit the beta(1) release.

Revision history for this message
PaulH (phd685) wrote :

I do not know what to do about this.I have searched everywhere but only found this similar report. I get a continual scroll and am unable to launch a clean KuBuntu 10.4 . I can see files on disk but it wont load.

15.xxxxxxx*/build /buildd /linux -2.6.32/drivers/hid/usbhid/hid-core:can't reset device mean
Can someone help?
Paul

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

PaulH,
   please file a new bug using 'ubuntu-bug linux' from the command line.

Thanks!

~JFo

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

Toby Smithe, 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.dell.com/support/troubleshooting/us/en/19/Product/studio-1537 an update is available for your BIOS (A11). 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-a11
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.