[ASUS M3A32-MVP DELUXE] suspend/resume failure

[Jim Patterson]

After suspending the system before retiring last night, it would not enable the display upon resume (using the <shift> key on this PC). The system had woken up, as I could hear the fan, but I cannot work without the display. I waited at least 1 minute but the monitor never came out of sleep mode. I finally reset the systm.

This is not a new issue. I've seen it persistently, on two different PCs I own, since 12.04.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-16-generic 3.8.0-16.26 [modified: boot/vmlinuz-3.8.0-16-generic]
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: jim 2040 F.... pulseaudio
 /dev/snd/controlC0: jim 2040 F.... pulseaudio
 /dev/snd/controlC1: jim 2040 F.... pulseaudio
CRDA:
 country CO:
  (2402 - 2472 @ 40), (3, 27)
  (5170 - 5250 @ 40), (3, 17)
  (5250 - 5330 @ 40), (3, 23), DFS
  (5735 - 5835 @ 40), (3, 30)
Date: Sun Apr 7 10:33:17 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=f3d69779-2779-47e6-9f55-e79bffb1b5cc
InstallationDate: Installed on 2013-04-06 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
InterpreterPath: /usr/bin/python3.3
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic root=UUID=788d972f-18cf-48d8-93fa-d851797f1936 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-16-generic N/A
 linux-backports-modules-3.8.0-16-generic N/A
 linux-firmware 1.104
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [System manufacturer System Product Name] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/26/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A32-MVP DELUXE
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.:bvr0801:bd12/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A32-MVPDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0]. You will need to install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc6-raring/

[Jim Patterson (jimp-launchpad-rs9z)]

I've re-tested using a kernel from v3.9-rc6-raring, specifically linux-image-3.9.0-030900rc6-generic_3.9.0-030900rc6.201304080035_amd64.deb . I'm still seeing the crash (which appears to be just a hung system as I can't see anything on the display).

Just to confirm:

jim@hobbes:~$ uname -a
Linux hobbes 3.9.0-030900rc6-generic #201304080035 SMP Mon Apr 8 04:36:25 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I'll tag as requested.

[Brad Figg (brad-figg)]

There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.

You can update to the latest kernel by simply running the following commands in a terminal window:
    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the
bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Jim Patterson (jimp-launchpad-rs9z)]

I tried the Kernel PPA but it didn't correct the problem. As asked I've moved back onto the Ubuntu 13.04 release, now at 3.8.0-26-generic, but after rebooting and going into Suspend, it acted the same way when I tried to wake up (<shift> would wake up the computer as the fan was running, but the monitor would stay in sleep mode and nothing else would happen).

[penalvch (penalvch)]

Jim Patterson, as per http://www.asus.com/Motherboards/M3A32MVP_DeluxeWiFiAP/#support_Download_5 an update is available for your BIOS (2202). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Jim Patterson (jimp-launchpad-rs9z)]

Just updated to the latest, 2202, and it does seem to resolve the issue. The system has suspended several times and woken up without any issues.

Thanks.

[penalvch (penalvch)]

Jim Patterson, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165774/comments/8 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.