WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()

Bug #459858 reported by Andreas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just tried to Suspend... When I restarted it was just a dark monitor. I had to reboot... by hardware...
I know there's a nvidia Issue with this. So, to me it didnt work out if the box.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andreas 2113 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Audigy2'/'SB Audigy 2 Platinum [SB0240P] (rev.4, serial:0x10021102) at 0xd800, irq 18'
   Mixer name : 'SigmaTel STAC9721,23'
   Components : 'AC97a:83847609'
   Controls : 214
   Simple ctrls : 49
Card1.Amixer.info:
 Card hw:1 'UART'/'MPU-401 UART at 0x330, irq 10'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Date: Sat Oct 24 17:57:46 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=cb456960-61b5-48be-99ef-06290cde4ffd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Beta i386 (20090929.2)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: ASUSTeK Computer INC. A7N8X-X
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=9b34dd53-f4b4-43d4-ba1d-b3e3b1d746d8 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 08/04/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A7N8X-X ACPI BIOS Rev 1011
dmi.board.name: A7N8X-X
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufactture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA7N8X-XACPIBIOSRev1011:bd08/04/2004:svnASUSTeKComputerINC.:pnA7N8X-X:pvrREV2.xx:rvnASUSTeKComputerINC.:rnA7N8X-X:rvrREV2.xx:cvnChassisManufactture:ct3:cvrChassisVersion:
dmi.product.name: A7N8X-X
dmi.product.version: REV 2.xx
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Andreas (anhyb) wrote :
Revision history for this message
Andreas (anhyb) wrote :

Hello,

THIS worked for me:

1.) Edit "/etc/X11/xorg.conf" like this (as root):

Section "Device"
        Driver "nvidia"
        Option "NvAGP" "1"
EndSection

2.) Edit the "/etc/default/acpi-support" like this (as root):

# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false

3.) Blacklist the agp-modules (look after them by typing: lsmod | grep agp)
     I did it by editing "/etc/modprobe.d/blacklist.conf" (as root) like this (just typing this at the end of the file):

blacklist agpgart
blacklist nvidia_agp

4.) Restart... and it worked for me!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Andreas,

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 9.448 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
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 417842, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
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.