Description of problem: System inoperable after (power-button) sleep Version-Release number of selected component (if applicable): vmlinuz-4.8.12-200.fc24.x86_64 How reproducible: so far 75% (3 out of 4 times did not recover) Steps to Reproduce: 1. turn system "off" by using power button to sleep it 2. turn power back on 3. enter password Actual results: System returns but the console window I always runs is "semi-transparent" not opaque like usual; mouse tracks but no other operations is possible - full power boot (using plug on wall) is requred Expected results: Normally I can use the system after a sleep without any further operations (enter password and GO). Additional info: I am NOT sure if the password is registering or not as I normally enter this while the screen is still black and powering up. I will try a few times to allow it to come up and then enter the password if I can. This started when I ran my weekly update and got 4.8.12 installed, I did another update after 2 days (hoping) but the OS stayed the same and the problem recurred after the 2nd sleep. This problem does not occur on my second (wife's) machine which has same OS but no graphics processor. Suspect it is related to graphics processor which has caused other reported systemd problems in past. Machine is a Dell - below is as much hardware information as I have last dnf patch was yesterday 12/13/2016 Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 58 Model name: Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz Stepping: 9 CPU MHz: 2212.463 CPU max MHz: 3200.0000 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 Display controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) 00:1f.0 ISA bridge: Intel Corporation B75 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 620 OEM] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) CPU min MHz: 1600.0000 BogoMIPS: 5988.12 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 6144K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts
Can you switch to a text console (e.g. ctrl-alt-f5)? Can you attach logs from before the reboot (journalctl -b-1)? Anyway, looks like a driver problem.
will look and see for both (ssh a possability I think) 2 sleep cycles and no failures - cause I am ready! :=] trying again ...
Created attachment 1232226 [details] resuts of journalctl -b-1 from system console before a reboot I hope this helps.
You have some custom scripts installed: Dec 13 13:07:12 rainbow systemd-sleep[5761]: /usr/lib/systemd/system-sleep/sleepWrap: line 13: [: suspend: integer expression expected Dec 13 13:07:12 rainbow systemd-sleep[5761]: /usr/lib/systemd/system-sleep/sleepWrap: line 14: [: missing `]' Dec 13 13:07:12 rainbow systemd-sleep[5761]: /usr/lib/systemd/system-sleep/sleepWrap: line 15: [: missing `]' Dec 13 13:07:12 rainbow systemd-sleep[5761]: Suspending system... Did you try without them? Also: Dec 14 07:59:04 rainbow org.gnome.Shell.desktop[1351]: Window manager warning: Failed to set power save mode for output DVII37: Permission denied Dec 14 07:59:04 rainbow org.gnome.Shell.desktop[1351]: Window manager warning: Failed to set power save mode for output DVII37: Permission denied This looks suspicious. Do you get this error too if the resume is successful? Maybe some selinux issue? Do you have selinux in enforcing mode?
egg on face for script, it has been working till this latest release - curious fixed (weird that is worked) As for also, I do not know but will look for another failure to find out.
Created attachment 1233160 [details] another journalctl -b-1
OOPS - adding the attachment lost all my notes here: Oh well. This problem started about a week ago when I upgraded from 4.8.10-200 -> 4.8.12-200 (I upgrade weekly) Before I had occasional problems coming back from sleep but the symptoms were different Before: the login screen had a dead (old) clock and did nothing Now: I type in my password while the screen is still powering up so it is black, but when up I have my standard background and standard terminal - but nothing works and the terminal is transparent I see no more problems with my sleepWrap script (which has been running for about 3 months, killing any sshd and vpnc sessions I forgot to shut down - it was working even with the logged errors you saw, but is now silently working) I also saw no recurrances of the power set failure you saw, but will continue to look for it. Thanks - let me know if there is anything more I can get you that might help. I know how hard it is to fix a bug that is "sometimes".
Created attachment 1234390 [details] another journalctl -b-1 (final) one more journalctl -b-1 running new kernel initramfs-4.8.14-200.fc24.x86_64.img It took five successful sleeps before this happened again. It is still there. I will send no more unless requested.
For the record, I have had "sleep return" issues with this particular system for over a year, through many revisions of Fedora. With this release, the problem happened more often than ever before. Now with vmlinuz-4.8.15-200.fc24.x86_64, I seem to have it less again, but it still happens. I have no way of knowing if this is software (not liking my hardware) or hardware as it comes and goes (sounds like hardware kind of). If there is anything I should look at, please let me know. I have just had my 8the successful sleep return so maybe the updates helped or I got lucky with hardware. At this point, I am just going to treat this as something to live with.
Final comment - if this helps. I see the translucent screen as the system goes to sleep. I do not have enough times to be sure, but I think the problem is actually occuring before SLEEP is entered.
100% for sure now. The "translucent" command tool always shows up when I put the machine to sleep BEFORE it actually sleeps. When I come back, X is hung and I must reboot to get it back. Normal sleep gives the same screen I would get if I used screen-saver.
problem continues. frequency is about 1 out of 3 times. No particular other notables. Since I have seen no postings here, I am assuming you all think it might be hardware. I have no way to confirm if it is hardware or software. But rebooting is not too painful so I guess that is what it is.
This is the same as bug 1380434. Sorry I don't know how to record as a duplicate. But yes this is getting more and more consistent. Now this happens about every 2nd time or more that I put the system to sleep. The only other thing that I can note from the journal is the following occurs a lot. cinnamon-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. It is not always cinnamon-session but the remainder of the error is the same message for all sorts of X related daemons.
this is the same as bug 1380434. I cannot figure how to mark as a duplicate - sorry.
*** This bug has been marked as a duplicate of bug 1380434 ***