GTX 580 - 375.20 - Suspending doesn't work with Wayland compositors
Hello, when I use GNOME 3.22 with Mutter from Git built with --enable-egl-device and suspend my PC I can't wake it back up. When I wake it up the fans start up the monitor stays black and after 2-3 seconds the PC gives up and does a regular reboot. I tried the same with Weston with EGLStreams support and here the PC does resume, but the display image is complete static random noise with no mouse pointer or anything making it unusable. In the Xorg session the PC suspends and resumes just fine, sometimes the wallpaper is scrambled, but just applying again fixes it and everything else works fine. Attached is the bug report from the resumed weston session, because I can't generate a bug report when the PC doesn't fully resume. When I look through the last log with "journalctl -b -1" the last message is simply "Suspending machine". I don't know if this is related, but on Wayland the monitor also doesn't enter Standby Mode, when I lock the session. It goes black, but is still on and I can't wake it back up. I reported that for the EGLStreams patchset for mutter here: https://bugzilla.gnome.org/show_bug.cgi?id=773629
Hello,

when I use GNOME 3.22 with Mutter from Git built with --enable-egl-device and suspend my PC I can't wake it back up. When I wake it up the fans start up the monitor stays black and after 2-3 seconds the PC gives up and does a regular reboot. I tried the same with Weston with EGLStreams support and here the PC does resume, but the display image is complete static random noise with no mouse pointer or anything making it unusable. In the Xorg session the PC suspends and resumes just fine, sometimes the wallpaper is scrambled, but just applying again fixes it and everything else works fine. Attached is the bug report from the resumed weston session, because I can't generate a bug report when the PC doesn't fully resume. When I look through the last log with "journalctl -b -1" the last message is simply "Suspending machine". I don't know if this is related, but on Wayland the monitor also doesn't enter Standby Mode, when I lock the session. It goes black, but is still on and I can't wake it back up. I reported that for the EGLStreams patchset for mutter here: https://bugzilla.gnome.org/show_bug.cgi?id=773629

#1
Posted 11/23/2016 10:24 PM   
For the benefit of others here who know more about this than I do, what are your detailed system specs? OS version? [code]lshw[/code]
For the benefit of others here who know more about this than I do, what are your detailed system specs?

OS version?

lshw

Stability forms the keystone of true performance. Accept no substitute.
Help others to help you. Discovery is curiosity's reward.

IBM Security Advisory on Intel Management Engine Vulnerability
Full Disclosure: AMD-PSP: fTPM Remote Code Execution via crafted EK certificate

Some use a PC to play fantasy games. Others use one to learn what real games are being played.

linuxmint-18.3-mate-64bit, *4.13.0-30-lowlatency | *XG-C100C (*PnP) *2018-01 C.U. for Win 10 1709 x64 (KB4056892) | SABERTOOTH 990FX R2.0 (UEFI 2901, 2016/08/05), CSM-->UEFI and **Legacy OpROM (**allows for the custom partitioning of SSDs & HDDs that will also work intact with up-to-date Vishera-capable PC-BIOS-based motherboards), no 'Secure' Boot or HPET | IOMMU Enabled | FX-8370, amd64-microcode_3.20171205.1_amd64.deb | CLP0587 with 1 x Venturi HP-14 PWM | KVR16E11K4/32 | STRIX-GTX960-DC2OC-4GD5 (nVidia 384.111). Resume from S3 works correctly in all regards. Hibernate does not. | GL2450HM, DVIDDMM10, ARMUNONB | 220-G2-0850-XR | DRW-24B1ST | PEXMSATA3422 (Firmware: 2.3.0.1065) with 2 x SMS200S3/120G in RAID 0 and 2 x ST3000DM001 in RAID 0 | 1 x ST6000DM001, 1 x ST2000DM001_Win 10 Pro 1709 x64 (SB950), 1 x ST6000DM001 (ASM1062A) | S252BU33R (Firmware Version: 101.01.01.09) with 2 x ST2000LM003, JU-P40511-S1 (uPD720201), JU-H40711-S1 (VIA VL811 ) | CM 690 II Advanced, HP-12 PWMs, HP-14 PWMs, FAN7X10TX3 | ST0026Z | Asus PCE-AC55BT (Intel 7260) PnP | Y-BF37 (Sleep key), SM50F76959

#2
Posted 11/24/2016 12:10 AM   
That's in the autogenerated bug report.
That's in the autogenerated bug report.

#3
Posted 11/24/2016 09:11 AM   
Scroll To Top

Add Reply