[Bug 1210029] New: Can't hibernate laptop Lenovo L14 Gen 3 AMD
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 Bug ID: 1210029 Summary: Can't hibernate laptop Lenovo L14 Gen 3 AMD Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: carlos.e.r@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 866050 --> http://bugzilla.opensuse.org/attachment.cgi?id=866050&action=edit journal using "Sleep State: Windows and Linux" Laptop can be suspended, but not hibernated. I am using "systemctl hibernate" as root. BIOS aka UEFI configuration has this selector: Sleep State: Windows and Linux vs Linux S3 hibernation In the first mode, screen goes to black for an instant, then pops for user password. I save the journal, and I see this: Apr 01 22:13:12 Beta.valinor kernel: Disabling non-boot CPUs ... Apr 01 22:13:12 Beta.valinor kernel: Wakeup pending. Abort CPU freeze I will attach the journal. I have been directed to read <https://wiki.archlinux.org/title/Power_management/Wakeup_triggers> and google that message, but so far, no success. On 15.4 I tried the second config option (Linux S3 hibernation) and it locked kernel hard, but journal was written. I will try again on 15.5 and report. I can also try kernel 6.2.8 from "Kernel:stable:Backports" on 15.4 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c1 --- Comment #1 from Carlos Robinson <carlos.e.r@opensuse.org> --- Ok, on 15.5, using BIOS setting "Sleep State: Linux S3 hibernation" behavior is different than I observed on 15.4. I'll mention than on 15.4 I use full disk encryption with discrete partitions, while 15.5 is just one ext4 root partition and another swap partition, non encrypted. Hibernation appears to succeed, but on restore I don't see it attempts to read the sap image, it boots fresh. I will attach both journals, from hibernation attempt, and fresh boot. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c2 --- Comment #2 from Carlos Robinson <carlos.e.r@opensuse.org> --- Created attachment 866051 --> http://bugzilla.opensuse.org/attachment.cgi?id=866051&action=edit journal of hibernation attempt using bios setting "Sleep State: Linux S3 hibernation" -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c3 --- Comment #3 from Carlos Robinson <carlos.e.r@opensuse.org> --- Created attachment 866052 --> http://bugzilla.opensuse.org/attachment.cgi?id=866052&action=edit oournal of fresh boot after hibernation attempt using bios setting "Sleep State: Linux S3 hibernation" -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c4 --- Comment #4 from Carlos Robinson <carlos.e.r@opensuse.org> --- Hibernation succeeds on Leap 15.4 with kernel 6.2.8 from "Kernel:stable:Backports". I was confused initially because grub prompts for encryption password twice, but it worked. Laicolasse:~ # journalctl --list-boots -4 953f80893ae14d0ca8461542274a8bf7 Wed 2023-03-29 21:25:15 CEST���Wed 2023-03-29 21:30:21 CEST -3 76004a2497fc438db28691417fc1390e Wed 2023-03-29 21:32:43 CEST���Wed 2023-03-29 21:39:33 CEST -2 8f44823f6dd645278c21d109dfef4340 Wed 2023-03-29 21:40:56 CEST���Wed 2023-03-29 22:18:38 CEST -1 1f88f85b017f4ca1894344e4a4357939 Wed 2023-03-29 22:20:30 CEST���Fri 2023-03-31 18:47:39 CEST 0 855834a651af439b83dc0a057fe72109 Sat 2023-04-01 23:06:57 CEST���Sat 2023-04-01 23:22:19 CEST Laicolasse:~ # journalctl -b 0 > /tmp/p0 list of journals proof it is a single session this Saturday :-) I will now attach this journal. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c5 --- Comment #5 from Carlos Robinson <carlos.e.r@opensuse.org> --- Created attachment 866053 --> http://bugzilla.opensuse.org/attachment.cgi?id=866053&action=edit journal of sucessfull hibernation using BIOS setting "Sleep State: Linux S3 hibernation" and kernel 6.2.8 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c7 --- Comment #7 from Carlos Robinson <carlos.e.r@opensuse.org> --- Er... no, Leap 15.4 with kernel 6.2.8 from "Kernel:stable:Backports", and switching the BIOS sleep mode to "Linux S3 hibernation", hibernation to disk works fine. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c8 --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- OK, then could you boot with no_console_suspend option and try hibernation/resume, and get the kernel log at resume from both working and non-working caess? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c9 --- Comment #9 from Carlos Robinson <carlos.e.r@opensuse.org> --- Ok. I can get the working case only on 15.4 with kernel 6.2.8. The non working case I can get 15.5 with your kernel for mt76. Is that ok? I can install another kernel if not. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c10 --- Comment #10 from Carlos Robinson <carlos.e.r@opensuse.org> --- Oh, in case it is of any interest, laptop beeped a moment ago and printed on all terminals: Laicolasse:~ # Message from syslogd@Laicolasse at Apr 4 09:58:05 ... kernel:[10684.097050][ C0] Uhhuh. NMI received for unknown reason 2c on CPU 0. Message from syslogd@Laicolasse at Apr 4 09:58:05 ... kernel:[10684.097056][ C0] Dazed and confused, but trying to continue Laicolasse:~ # Laicolasse:~ # uname -a Linux Laicolasse.valinor 6.2.8-lp154.3.gc9a94ac-default #1 SMP PREEMPT_DYNAMIC Tue Mar 28 07:54:15 UTC 2023 (c9a94ac) x86_64 x86_64 x86_64 GNU/Linux Laicolasse:~ # grep "NAME=\|ID=" /etc/os-release NAME="openSUSE Leap" ID="opensuse-leap" VERSION_ID="15.4" PRETTY_NAME="openSUSE Leap 15.4" CPE_NAME="cpe:/o:opensuse:leap:15.4" Laicolasse:~ # otherwise, running fine. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c11 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- (In reply to Carlos Robinson from comment #9)
The non working case I can get 15.5 with your kernel for mt76.
Is that ok? I can install another kernel if not.
That's OK, please test with that kernel. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c12 --- Comment #12 from Carlos Robinson <carlos.e.r@opensuse.org> --- Created attachment 866094 --> http://bugzilla.opensuse.org/attachment.cgi?id=866094&action=edit journal of hibernation, Leap 15.4 kernel 6.2.8-lp154.3.gc9a94ac-default with no_console_suspend -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c13 --- Comment #13 from Carlos Robinson <carlos.e.r@opensuse.org> --- Created attachment 866096 --> http://bugzilla.opensuse.org/attachment.cgi?id=866096&action=edit journal of failed hibernation, Leap 15.5 kernel 5.14.21-150500.3.gad9a743-default with no_console_suspend -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c14 --- Comment #14 from Carlos Robinson <carlos.e.r@opensuse.org> --- Created attachment 866097 --> http://bugzilla.opensuse.org/attachment.cgi?id=866097&action=edit journal after failed hibernation, Leap 15.5 kernel 5.14.21-150500.3.gad9a743-default with no_console_suspend -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c15 --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- Thanks. Is the 15.5 tested on the whole Leap 15.5 system? Or it's Leap 15.5 kernel on top of the (working) 15.4 system? At this point, please try to keep the user-space same as working, but change only the kernel; that is, boot with Leap 15.5 kernel while keeping the rest as the working-hibernation environment (15.4). Then retest with no_console_suspend, and get the kernel log with the failing case. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c16 --- Comment #16 from Takashi Iwai <tiwai@suse.com> --- ... or vice versa, check Leap 15.4 kernel on top of the Leap 15.5 system and verify whether the hibernation still works with it or not. I'm asking it to exclude the possibility of a regression by some other component than the kernel itself. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c17 --- Comment #17 from Carlos Robinson <carlos.e.r@opensuse.org> --- For the record, journalctl almost provoked me to submit a wrong journal log. Beta:~ # journalctl --list-boots -8 bff43e3dd735461f9c2f451dca7a8486 Sat 2023-04-01 22:47:51 CEST���Sat 2023-04-01 22:51:11 CEST -7 dec62252db9c46ebb99c7fd03d32a4ae Sat 2023-04-01 22:51:40 CEST���Sat 2023-04-01 23:05:37 CEST -6 6409ed7781ea4b81bf07f3f5a4d936a4 Sun 2023-04-02 20:33:34 CEST���Sun 2023-04-02 20:55:18 CEST -5 babb6dd2ea3c459ea9ece85a11559b0a Sun 2023-04-02 20:55:44 CEST���Sun 2023-04-02 21:08:05 CEST -4 8de7405b36ac41e285b414cf03398c2d Sun 2023-04-02 21:08:31 CEST���Mon 2023-04-03 03:35:48 CEST -3 152f444cc6fc44b88966d65084e6ba73 Tue 2023-04-04 11:51:35 CEST���Tue 2023-04-04 12:04:15 CEST -2 b57a7bc3a06a4ba8b4e485aa810c3b35 Tue 2023-04-04 12:04:47 CEST���Tue 2023-04-04 12:08:21 CEST -1 2a3034c8668a4897b0e857e611bde4ee Tue 2023-04-04 12:09:03 CEST���Tue 2023-04-04 12:13:36 CEST 0 8d19714585b04128a46562b917a621fb Tue 2023-04-04 12:14:13 CEST���Tue 2023-04-04 12:17:53 CEST Beta:~ # The command "journalctl -b0" produces the right log: Apr 04 12:14:13 Beta kernel: Linux version 5.14.21-150500.3.gad9a743-default (geeko@buildhost)... But "journalctl -b1" produces apparently log #8 instead: Apr 01 22:47:51 Beta kernel: Linux version 5.14.21-150500.1.ga8add28-default (geeko@buildhost) ... I had to use "journalctl -b 8d19714585b04128a46562b917a621fb" instead. If one of the provided logs is wrong, that is the reason. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c18 --- Comment #18 from Carlos Robinson <carlos.e.r@opensuse.org> --- Ok, there you have the logs (journal). Succesful hibernation with Kernel:stable:Backports, Leap 15.4 journal of hibernation, Leap 15.4 kernel 6.2.8-lp154.3.gc9a94ac-default with no_console_suspend (318.94 KB, text/plain) Failed hibernation, on Leap 15.5: journal of failed hibernation, Leap 15.5 kernel 5.14.21-150500.3.gad9a743-default with no_console_suspend (295.70 KB, text/plain) journal after failed hibernation, Leap 15.5 kernel 5.14.21-150500.3.gad9a743-default with no_console_suspend (288.55 KB, text/plain) -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c19 --- Comment #19 from Carlos Robinson <carlos.e.r@opensuse.org> --- (In reply to Takashi Iwai from comment #15)
Thanks.
Is the 15.5 tested on the whole Leap 15.5 system? Or it's Leap 15.5 kernel on top of the (working) 15.4 system?
It is a different partition, with a fresh install of 15.5, complete. I called the install "Beta". That is, I have a full Leap 15.4 booting with Kernel:stable:Backports, named "Laicolasse", that can hibernate, and I have a full 15.5 install (called "Beta") with your modified kernel for the WiFi problem, that can not hibernate.
At this point, please try to keep the user-space same as working, but change only the kernel; that is, boot with Leap 15.5 kernel while keeping the rest as the working-hibernation environment (15.4). Then retest with no_console_suspend, and get the kernel log with the failing case.
Ok, I suppose I can install Kernel:stable:Backports to Beta system. Now that I have "Laicolasse" working (my production partition) I don't want to touch it. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c20 --- Comment #20 from Carlos Robinson <carlos.e.r@opensuse.org> --- Created attachment 866102 --> http://bugzilla.opensuse.org/attachment.cgi?id=866102&action=edit Session on Beta machine using backports kernel. Read comments. Notice that return from hibernation on Beta machine using backports kernel 6.2.9 failed, and on next boot the MOK enrollment display appeared, but apparently did nothing. The production partition is using kernel 6.2.8. YaST did something weird when doing the package switch to backports repo. First it said it could not download and aborted. Next time it refused to do the switch. I had to tick the kernel, but the other packages in the repo did not switch. zypper dup --from also refused to switch everything. I have a backup copy of kernel 6.2.8 which is working on production partition and can probably update to it. Current package list: Beta:~ # rpm -qa | grep kernel kernel-firmware-chelsio-20230320-lp154.2.1.noarch kernel-firmware-nvidia-20230320-lp154.2.1.noarch kernel-firmware-ueagle-20230320-lp154.2.1.noarch kernel-firmware-ath10k-20230320-lp154.2.1.noarch kernel-firmware-media-20230320-lp154.2.1.noarch kernel-firmware-nfp-20230320-lp154.2.1.noarch kernel-firmware-amdgpu-20230320-lp154.2.1.noarch kernel-firmware-marvell-20230320-lp154.2.1.noarch kernel-firmware-realtek-20230320-lp154.2.1.noarch kernel-firmware-mediatek-20230320-lp154.2.1.noarch kernel-firmware-all-20230320-lp154.2.1.noarch kernel-firmware-ti-20230320-lp154.2.1.noarch kernel-firmware-liquidio-20230320-lp154.2.1.noarch kernel-default-optional-5.14.21-150500.46.1.x86_64 kernel-firmware-radeon-20230320-lp154.2.1.noarch kernel-firmware-i915-20230320-lp154.2.1.noarch kernel-firmware-usb-network-20230320-lp154.2.1.noarch kernel-firmware-prestera-20230320-lp154.2.1.noarch kernel-firmware-brcm-20230320-lp154.2.1.noarch kernel-firmware-iwlwifi-20230320-lp154.2.1.noarch kernel-default-5.14.21-150500.46.1.x86_64 kernel-firmware-serial-20230320-lp154.2.1.noarch kernel-firmware-dpaa2-20230320-lp154.2.1.noarch kernel-firmware-qlogic-20230320-lp154.2.1.noarch kernel-firmware-platform-20230320-lp154.2.1.noarch kernel-firmware-bnx2-20230320-lp154.2.1.noarch kernel-firmware-network-20230320-lp154.2.1.noarch kernel-firmware-ath11k-20230320-lp154.2.1.noarch purge-kernels-service-0-150200.8.6.1.noarch kernel-firmware-qcom-20230320-lp154.2.1.noarch kernel-firmware-bluetooth-20230320-lp154.2.1.noarch kernel-firmware-mwifiex-20230320-lp154.2.1.noarch kernel-default-6.2.9-lp154.4.1.g8db91ce.x86_64 kernel-firmware-atheros-20230320-lp154.2.1.noarch kernel-firmware-mellanox-20230320-lp154.2.1.noarch kernel-firmware-sound-20230320-lp154.2.1.noarch kernel-default-extra-5.14.21-150500.46.1.x86_64 kernel-firmware-intel-20230320-lp154.2.1.noarch Beta:~ # -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c21 --- Comment #21 from Carlos Robinson <carlos.e.r@opensuse.org> --- well, I don't understand it. Leap 15.5 (full install) using kernel 6.2.8-lp154.3.gc9a94ac-default fails to recover from hibernation, same as 6.2.9, whereas Leap 15.4 (full install) with kernel 6.2.8 succeeds. That's the information I have, I don't know how to get better information for you. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c22 --- Comment #22 from Takashi Iwai <tiwai@suse.com> --- (In reply to Carlos Robinson from comment #21)
well, I don't understand it. Leap 15.5 (full install) using kernel 6.2.8-lp154.3.gc9a94ac-default fails to recover from hibernation, same as 6.2.9, whereas Leap 15.4 (full install) with kernel 6.2.8 succeeds.
That's what I was afraid of. This might be rather a problem in user-space side, e.g. dracut. To be sure, could you try the following? - Download kernel-default-5.14.21-150500.3.1.gad9a743.x86_64.rpm from my OBS repo - Install it on the Leap 15.4 system directly via zypper install: zypper in kernel-default-5.14.21-150500.3.1.gad9a743.x86_64.rpm - Retest hibernation. I guess this may work. Once after testing, you can remove the kernel again: zypper rm kernel-default-5.14.21-150500.3.1.gad9a743 Once after the test, you can uninstall the test kernel package again via zypper remove (with the exact kernel version). -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c23 --- Comment #23 from Carlos Robinson <carlos.e.r@opensuse.org> --- You are right, it worked (albeit no wifi). Do you want the journal? I guess I could change this production partition to use this test kernel instead of the Kernel:stable:Backports, if I also change the firmware files. Ok, what next? how can we find out what userspace tool is blocking hibernation on the 15.5 Beta partition? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c24 --- Comment #24 from Takashi Iwai <tiwai@suse.com> --- I'd try to *downgrade* dracut on Leap 15.5 partition to the version of Leap 15.4 at first. That's the first suspect. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c25 --- Comment #25 from Carlos Robinson <carlos.e.r@opensuse.org> --- No luck. [If hurried, skip to the end of this comment: problem found] I removed the "Kernel:stable:Backports" repo, fully changed to kernel 5.14.21-150500.3.gad9a743-default, and run "mkinitrd". Then rebooted, and attempted hibernation. Installed dracut and kernel packages are: Beta:~ # rpm -qa | grep -i dracut plymouth-dracut-0.9.5~git20210406.e554475-150400.3.8.1.noarch dracut-mkinitrd-deprecated-055+suse.331.g05b9ccb7-150400.3.16.1.x86_64 dracut-055+suse.331.g05b9ccb7-150400.3.16.1.x86_64 Beta:~ # rpm -qa | grep -i kernel kernel-firmware-qlogic-20230210-150500.1.1.noarch kernel-firmware-serial-20230210-150500.1.1.noarch kernel-firmware-network-20230210-150500.1.1.noarch kernel-firmware-platform-20230210-150500.1.1.noarch kernel-firmware-bluetooth-20230210-150500.1.1.noarch kernel-firmware-chelsio-20230210-150500.1.1.noarch kernel-default-5.14.21-150500.3.1.gad9a743.x86_64 kernel-firmware-ueagle-20230210-150500.1.1.noarch kernel-firmware-ath10k-20230210-150500.1.1.noarch kernel-firmware-mellanox-20230210-150500.1.1.noarch kernel-firmware-amdgpu-20230210-150500.1.1.noarch kernel-firmware-nfp-20230210-150500.1.1.noarch kernel-firmware-atheros-20230210-150500.1.1.noarch kernel-firmware-realtek-20230210-150500.1.1.noarch kernel-firmware-intel-20230210-150500.1.1.noarch kernel-default-optional-5.14.21-150500.46.1.x86_64 kernel-firmware-sound-20230210-150500.1.1.noarch kernel-firmware-marvell-20230210-150500.1.1.noarch kernel-default-extra-5.14.21-150500.3.1.gad9a743.x86_64 kernel-firmware-liquidio-20230210-150500.1.1.noarch kernel-default-optional-5.14.21-150500.3.1.gad9a743.x86_64 kernel-default-5.14.21-150500.46.1.x86_64 kernel-firmware-ti-20230210-150500.1.1.noarch kernel-firmware-mediatek-20230210-150500.1.1.noarch kernel-firmware-all-20230210-150500.1.1.noarch kernel-firmware-usb-network-20230210-150500.1.1.noarch kernel-firmware-prestera-20230210-150500.1.1.noarch kernel-firmware-brcm-20230210-150500.1.1.noarch kernel-firmware-radeon-20230210-150500.1.1.noarch kernel-firmware-i915-20230210-150500.1.1.noarch purge-kernels-service-0-150200.8.6.1.noarch kernel-firmware-dpaa2-20230210-150500.1.1.noarch kernel-firmware-iwlwifi-20230210-150500.1.1.noarch kernel-firmware-ath11k-20230210-150500.1.1.noarch kernel-firmware-bnx2-20230210-150500.1.1.noarch kernel-firmware-nvidia-20230210-150500.1.1.noarch kernel-firmware-qcom-20230210-150500.1.1.noarch kernel-firmware-media-20230210-150500.1.1.noarch kernel-firmware-mwifiex-20230210-150500.1.1.noarch kernel-default-extra-5.14.21-150500.46.1.x86_64 Beta:~ In case of needing the journals, they are: Hibernation: -1 dfb94e024448402dbc6378800e61317f Thu 2023-04-06 22:22:42 CEST���Thu 2023-04-06 22:27:13 CEST next boot_ 0 a4a5928cd90848d285a23d0ffd559669 Thu 2023-04-06 22:27:54 CEST���Thu 2023-04-06 22:39:05 CEST Wait. I'm seeing something strange in the journal, first line, the kernel load line... Beta:/Other # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="splash=verbose preempt=full security=apparmor mitigations=auto no_console_suspend" Beta:/Other # grep GRUB_CMDLINE_LINUX_DEFAULT /Other/etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-label/Swap preempt=full quiet security=apparmor mitigations=auto no_console_suspend" Beta:/Other # There is no "resume" entry! This is YaST doing. :-( And hibernate process did not check the error. Shit! :-( (excuse me). [...] Bingo! Now it works. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 http://bugzilla.opensuse.org/show_bug.cgi?id=1210029#c26 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |YaST2 Assignee|kernel-bugs@opensuse.org |yast2-maintainers@suse.de QA Contact|qa-bugs@suse.de |jsrain@suse.com --- Comment #26 from Takashi Iwai <tiwai@suse.com> --- OK, let's reassign to YaST guys for further investigation. I thought YaST had some mechanism to detect and add/remove resume=xxx option. Maybe the judgement wasn't correct in your case? -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com