[Bug 1083774] New: Suspend and hibernate do not work
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 Bug ID: 1083774 Summary: Suspend and hibernate do not work Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Macintosh OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: indigojo@blogistan.co.uk QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Build Identifier: I am using an iMac, 21.5in model 16,2 (Retina) with KDE Plasma Desktop 5.12.1 as supplied with OpenSUSE Leap 15.0 Beta. Suspend and hibernate both do not work on this system. With Suspend, the screen goes blank and no keypress or mouse action will cause it to come back on (my keyboard is an Apple USB keyboard). With Hibernate, the application windows disappear leaving nothing but a mouse pointer; as my mouse is a Bluetooth device, this becomes inoperable. In both cases, a hard reboot is necessary. Reproducible: Always Steps to Reproduce: 1. Open KDE launcher menu. 2. Select Leave from the set of icons at the bottom 3. Select Suspend or Hibernate 4. Wait for screen to go blank 5. Press any button or the mouse button, as is usual when restarting a system from Suspend/Hibernate, or the power button on the back. Actual Results: When you press keys on the keyboard or the power button, nothing happens. Expected Results: I should expect the screen should return to how it was before I engaged Suspend or Hibernate. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 Matthew Smith <indigojo@blogistan.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |Leap 15.0 OS|Other |SUSE Other -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c2 --- Comment #2 from Matthew Smith <indigojo@blogistan.co.uk> --- Created attachment 762787 --> http://bugzilla.opensuse.org/attachment.cgi?id=762787&action=edit HWinfo output -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c3 --- Comment #3 from Matthew Smith <indigojo@blogistan.co.uk> --- Installed the latest kernel (4.12.14-lp150.5.3) from the repo -- I presume you meant this one: http://download.opensuse.org/repositories/Kernel:/openSUSE-15.0/standard/x86... The issue still persists: it is still impossible to wake from Suspend with random keypresses or the power button, and a hard reboot is required. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c4 --- Comment #4 from Matthew Smith <indigojo@blogistan.co.uk> --- Hibernate problem still persists. Screen blanks except for the mouse pointer (which will not move as it's a Bluetooth mouse). Press a few keys and the screen goes blank, press a few more and the dead mouse pointer comes back. Still requires a hard reboot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- OK, thanks. Since it's a crash, maybe the best option would be to catch the crash dump. Could you try to enable kdump? You might need to increase the RAM size for crash kernel, as YaST often sets up too tightly. Before the actual testing, check whether kdump works via sysrq, e.g. echo c > /proc/sysrq-trigger This will crash manually, and if everything is right, the kdump should be kicked off. Once if you get a proper kdump at the crash, please upload dmesg.txt from the corresponding /var/crash/* entry. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c6 --- Comment #6 from Matthew Smith <indigojo@blogistan.co.uk> --- How big do you suggest setting the crash kernel size? When I try to start kdump it fails for lack of memory. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c7 --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- (In reply to Matthew Smith from comment #6)
How big do you suggest setting the crash kernel size? When I try to start kdump it fails for lack of memory.
It depends on the environment. I'd double or so for YaST's suggestsion (e.g. 256MB for 150MB). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c8 --- Comment #8 from Matthew Smith <indigojo@blogistan.co.uk> --- Do I just need to set the parameter and then reboot with Kdump enabled? When I ran "systemctl status kdump.service" as root, this was the output: ● kdump.service - Load kdump kernel and initrd Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled Active: active (exited) since Wed 2018-03-07 16:07:43 GMT; 2min 57s ago Process: 1989 ExecStart=/lib/kdump/load.sh --update (code=exited, status=0/SUCCESS) Main PID: 1989 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/kdump.service Mar 07 16:07:43 linux-anyv systemd[1]: Starting Load kdump kernel and initrd... Mar 07 16:07:43 linux-anyv load.sh[1989]: kexec_file_load failed: Key was rejected by serv Mar 07 16:07:43 linux-anyv kdump[2071]: Loaded kdump kernel: /sbin/kexec -p /boot/vmlinuz- Mar 07 16:07:43 linux-anyv systemd[1]: Started Load kdump kernel and initrd. When I tried suspending after rebooting with a debug kernel with kdump enabled (through Yast), it also would not wake up but I didn't get a /var/crash entry; that directory is empty. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- (In reply to Matthew Smith from comment #8)
Do I just need to set the parameter and then reboot with Kdump enabled? When I ran "systemctl status kdump.service" as root, this was the output:
● kdump.service - Load kdump kernel and initrd Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled Active: active (exited) since Wed 2018-03-07 16:07:43 GMT; 2min 57s ago Process: 1989 ExecStart=/lib/kdump/load.sh --update (code=exited, status=0/SUCCESS) Main PID: 1989 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/kdump.service
Mar 07 16:07:43 linux-anyv systemd[1]: Starting Load kdump kernel and initrd... Mar 07 16:07:43 linux-anyv load.sh[1989]: kexec_file_load failed: Key was rejected by serv Mar 07 16:07:43 linux-anyv kdump[2071]: Loaded kdump kernel: /sbin/kexec -p /boot/vmlinuz- Mar 07 16:07:43 linux-anyv systemd[1]: Started Load kdump kernel and initrd.
The first two lines show that kdump tried kexec_file_load syscall, and it failed. This is OK, and expected: the syscall is only for the signed kernels, while you're using an unsigned one. Then the next line shows that kdump tried the traditional method, and it succeeded. So far, so good.
When I tried suspending after rebooting with a debug kernel with kdump enabled (through Yast), it also would not wake up but I didn't get a /var/crash entry; that directory is empty.
The kdump can't always catch the crash. It can dump only when the kernel goes to panic mode. If the machine gets stuck in a different way or reboots immediately by some reason (e.g. writing invalid memory address), the kernel can't catch it, unfortunately. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c10 --- Comment #10 from Matthew Smith <indigojo@blogistan.co.uk> --- I followed the advice on this page: https://en.opensuse.org/SDB:Installation_on_a_Mac#Suspend_to_RAM After doing this and trying to suspend, when I pressed the power button once it did nothing; however, I pressed it again and after a few seconds, the machine rebooted. (Not a long press as is usually needed to force a reboot on the iMac.) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1083774 http://bugzilla.opensuse.org/show_bug.cgi?id=1083774#c11 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- Thanks, this sounds more like an issue you can't catch in kernel, then. The spurious reboot was somehow introduced in SLE15 kernel, as it seems, although I couldn't reproduce it on my Dell laptop with Skylake. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com