[ASUS Z87-PRO] suspend/resume failure

Bug #1299007 reported by dva20
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

none

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.40
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dv 2456 F.... pulseaudio
 /dev/snd/controlC0: dv 2456 F.... pulseaudio
Date: Wed Mar 26 19:56:33 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=c82b44c7-2b1a-4565-aee6-c53440dbb517
InterpreterPath: /usr/bin/python3.4
MachineType: ASUS All Series
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=9be1895a-72c0-4e9d-bb6f-6f7cf7d1beac 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.13.0-19-generic N/A
 linux-backports-modules-3.13.0-19-generic N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [ASUS All Series] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1405
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-PRO
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.:bvr1405:bd08/19/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

Revision history for this message
dva20 (dva20) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
penalvch (penalvch) wrote : Re: [ASUS All Series] suspend/resume failure

dva20, as per http://www.asus.com/Motherboards/Z87PRO/HelpDesk_Download/ an update to your BIOS is available (1802). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, 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

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

tags: added: bios-outdated-1802
summary: - [ASUS All Series] suspend/resume failure
+ [ASUS Z87-PRO] suspend/resume failure
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
Revision history for this message
Sam (sr897) wrote :

I have the same issue with Asus Z87-Pro motherboard. Running a newer BIOS and newer kernel.

Command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
Output:
    2103
    08/18/2014
I believe 2103 is the latest BIOS for this motherboard.

Changed in linux (Ubuntu):
status: Expired → Incomplete
Revision history for this message
Sam (sr897) wrote :

Debug info for Kernel 4.15.0.20.21

https://wiki.ubuntu.com/DebuggingKernelSuspend
Debugging information to provide in the bug report

Kernel 4.15.0.20.21
=====

1. Issue occurs with resume from 'Suspend to ram' (not hibernate).

2. Suspend action initiated by clicking Suspend in the GUI.

3. Resume initiated by pressing power button on PC case.

4. Attached.

5. (echo freezer > /sys/power/pm_test) UI froze for few seconds. System returned to normal operation after few seconds.

6. (echo devices > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). Display switched on again - showed Gnome UI in the same state as immediately before suspend. System not responsive. Caps-lock button not responding; USB keyboard remove-reattach not effective. Rebooted manually (cycled power).
After display switched on again; system started to respond to ping from network. Could not connect via ssh, despite being able to ping.

7. (echo platform > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). Display switched on again - showed Gnome UI in the same state as immediately before suspend. System not responsive. Caps-lock button not responding; USB keyboard remove-reattach not effective. Rebooted manually (cycled power).

8. (echo processors > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). Display switched on again - showed Gnome UI in the same state as immediately before suspend. System not responsive. Caps-lock button not responding; USB keyboard remove-reattach not effective. Rebooted manually (cycled power).

9. (echo core > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). Display switched on again - showed Gnome UI in the same state as immediately before suspend. System not responsive. Caps-lock button not responding; USB keyboard remove-reattach not effective. Rebooted manually (cycled power).

10. (echo none > /sys/power/pm_test) Display switched off. All fans powered off (CPU fan, PSU fan). Standby LED flashing on PC case. Resume initiated by pressing power button on PC case. Display remained off - LCD monitor standby LED flashing. System not responsive. Caps-lock button not responding; USB keyboard remove-reattach not effective. Rebooted manually (cycled power).

11. Unable to execute cat after reboot.
sudo cat /sys/kernel/debug/suspend_stats
cat: /sys/kernel/debug/suspend_stats: Operation not permitted

Revision history for this message
Sam (sr897) wrote :

Debug info for Kernel 4.20.0-042000

https://wiki.ubuntu.com/DebuggingKernelSuspend
Debugging information to provide in the bug report

Kernel 4.20.0-042000
=====

1. Issue occurs with resume from 'Suspend to ram' (not hibernate).

2. Suspend action initiated by clicking Suspend in the GUI.

3. Resume initiated by pressing power button on PC case.

4. Attached.

5. (echo freezer > /sys/power/pm_test) UI froze for few seconds. System returned to normal operation.

6. (echo devices > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). System returned to normal operation after few seconds.

7. (echo platform > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). System returned to normal operation after few seconds.

8. (echo processors > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). System returned to normal operation after few seconds.

9. (echo core > /sys/power/pm_test) Display switched off for few seconds. Standby flashing LED on PC case not observed (remained in solid 'ON' state). System returned to normal operation after few seconds.

10. (echo none > /sys/power/pm_test) Display switched off. All fans powered off (CPU fan, PSU fan). Standby LED flashing on PC case. Resume initiated by pressing power button on PC case. Display remained off - LCD monitor standby LED flashing. System not responsive. Caps-lock button not responding; USB keyboard remove-reattach not effective. Rebooted manually (cycled power).

11. suspend_stats output after successful restore at step 6 (devices) provided.

Notably, on this kernel version system returns to normal operation at step 6 (echo devices > /sys/power/pm_test). On kernel 4.15.0.20.21, system does not restore.
However, system still does not restore from step 10 (echo none > /sys/power/pm_test).

Revision history for this message
penalvch (penalvch) wrote :

Sam (sr897), as the root cause of this report isn't confirmed to be solely dependent on the motherboard, it is most helpful if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Also, please note as per the article https://wiki.ubuntu.com/DebuggingKernelSuspend manually attached files should be uncompressed and untarred (not zipped, gzipped, etc.).

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

If "echo none > /sys/power/pm_test" doesn't work then it can be a platform firmware (i.e. BIOS) issue.

Upgrade the BIOS may help.

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.