Description of problem: With a newly installed mga8 on a mga7 computer, hibernation does not work anymore. More precisely hibernating (for example via "systemctl hibernate") seems ok. Yet it reboots "normally", ignoring the stored image Comparing this mga8 computer with another "unmigrated" mga7 computer reveals that the "resume" module in dracut is missing, replaced by "kernel-modules-extra" A workaround is to manually add the module in 51-mageia-resume.conf #cat /etc/dracut.conf.d/51-mageia-resume.conf add_device+=" UUID=2b1f437b-3e28-4f03-adce-19e79a021be8 " add_dracutmodules+=" resume " localhost dracut.conf.d # dracut -fv Then hibernating works again.
Hi, thanks for reporting this bug.* Reproduced. I put my system to hibernate state (leaving a LibreOffice and Firefox opened to make sure the difference). Rebooting leads me to sddm asking me for new session, no LibreOffice nor Firefox window opened... Raising priority and severity as putting a system to hibernate and to be not able to restore session can lead to a potential data loss for unsaved work. Assigned to the package maintainer for Cauldron and MGA8TOO. (Please set the status to 'assigned' if you are working on it)
Severity: minor => criticalComponent: Installer => RPM PackagesTarget Milestone: --- => Mageia 8Whiteboard: (none) => MGA8TOOAssignee: bugsquad => pkg-bugsKeywords: (none) => FOR_ERRATA8CC: (none) => mageia, ouaurelien, thierry.vignaudPriority: Normal => HighSource RPM: dracut => dracut-051-4.mga8.src.rpmVersion: 8 => Cauldron
CC: (none) => fri
This is severe. @ Aurelien, did you try the suggested workaround?
Tried and it works!
Great. As it is severe and much wanted, it deserves a subchapter: https://wiki.mageia.org/en/Mageia_8_Errata#Hibernation
Keywords: FOR_ERRATA8 => IN_ERRATA8
Summary: Hibernation doesn't work after installation from Mageia-8-x86_64.iso => Resuming from hibernation instead start fresh; user loose work
I confirm the bug and that the workaround works.
CC: (none) => christophe.nanteuil
I can confirm this happening on my HP Probook 6550b. Fortunately, I don't do much of any critical work on this laptop. The two incidents I remember were when I was reading my morning newspaper. I was called away, and closed the lid to conserve the battery until I returned. LEDs indicated the data was being saved, but when I went to resume it did a cold boot. All I had to do was re-download the newspaper, but still, it was a bit annoying. Since it's not critical for me I will be leaving this alone, so I can have an untouched system ready to test the update that fixes this when it's sent to QA.
CC: (none) => andrewsfarm
There's an upstream issue for this: https://github.com/dracutdevs/dracut/issues/924 I poked the issue and I'll talk to the developer working on the issue after the Easter holiday in Germany is over.
CC: (none) => ngompa13
CC: (none) => filip.komar
Verified problem and fix on mga8 Plasma 64 bit installed by classical install, * upgraded to cauldron * since a while, on Dell Precision M4400. Partitioning: Dual boot w MSW10, and using LVM. Verified "add_dracutmodules" line is missing: # cat /etc/dracut.conf.d/51-mageia-resume.conf add_device+=" /dev/vg-M4400/lv_swap " Added the missing line by # echo 'add_dracutmodules+=" resume "' >> /etc/dracut.conf.d/51-mageia-resume.conf Then # dracut -fv And now suspend-resume works :)
Added the procedure in errata.
(In reply to Thomas Andrews from comment #6) > > Since it's not critical for me I will be leaving this alone, so I can have > an untouched system ready to test the update that fixes this when it's sent > to QA. It now becomes desirable for me to have hibernation functioning on my production install on this hardware, so since it's been months with no news I have used copy-and-paste to apply the workaround from errata, and indeed, it still works. Should an upstream fix show up, I can still test it on this hardware, as I now have two other M8 installs on it.
In instal from XFCE 64 fix also works on my PC.
(In reply to Morgan Leijström from comment #8) > Verified problem and fix on mga8 Plasma 64 bit installed by classical > install, > * upgraded to cauldron * since a while, on Dell Precision M4400. > > Partitioning: Dual boot w MSW10, and using LVM. > > > Verified "add_dracutmodules" line is missing: > # cat /etc/dracut.conf.d/51-mageia-resume.conf > add_device+=" /dev/vg-M4400/lv_swap " > > > Added the missing line by > # echo 'add_dracutmodules+=" resume "' >> > /etc/dracut.conf.d/51-mageia-resume.conf > > Then > # dracut -fv > > > And now suspend-resume works :) Confirming, that it works on HP Probook 430 G5.
CC: (none) => joelp
Description of problem: With a newly installed mga8 on an i7 8770 computer, hibernation does not work. I have read the Wiki https://wiki.mageia.org/en/Mageia_8_Errata item Miscellaneous - Hibernation. The installed package dracut-051-4.mga8.x86_64.rpm has the file /etc/dracut.conf.d/51-mageia-resume.conf listed but not packaged. Thus, I had crated this file using the suggested command line: echo 'add_dracutmodules+=" resume "' >> /etc/dracut.conf.d/51-mageia-resume.conf After that, I had run dracut -fv as is suggested in the Wiki. Finally, the hibernation have been working. Should the dracut-051-4.mga8.x86_64.rpm package be updated?
CC: (none) => jpaulo
The file is created by /usr/lib/libDrakX/any.pm from the package drakxtools-backend-18.45-1.mga8 Reassigning to mageiatools group.
CC: (none) => davidwhodginsAssignee: pkg-bugs => mageiatools
Confirming here for cauldron as well.
CC: (none) => ftg
Checking the upstream bug report referenced in comment 7, there is now (as of two weeks ago) a fix for this bug in dracut.
I had made the workaround change, but a recent update reverted it, so it has not been incorporated in current dracut.
Setting for errata 9 - remove if it gets fixed before release.
Target Milestone: Mageia 8 => Mageia 9Keywords: (none) => FOR_ERRATA9
(In reply to Frank Griffin from comment #17) > I had made the workaround change, but a recent update reverted it, so it has > not been incorporated in current dracut. Yes, because there hasn't been a new release of dracut yet. Anyway, I've just tested the supposed fix, and it doesn't work. I've reported that upstream.
I don't get it. The workaround worked for me (and others) for weeks. Then it disappeared from the 51* file with a cauldron update. I put it back, and overnight today my laptop powered off again with the lid shut. But when I checked the 51* file, the workaround is still there.
Should be fixed in dracut-057-4.mga9. To test, remove the workaround from /etc/dracut.conf.d/51-mageia-resume.conf and run "dracut -f".
Test worked. Looks fine now, thanks.
Nice Can it get fixed in mga8 too?
Target Milestone: Mageia 9 => ---Version: Cauldron => 8Keywords: FOR_ERRATA9 => (none)
(In reply to Frank Griffin from comment #22) > Test worked. Looks fine now, thanks. And now, overnight with lid closed, powered down again. Did something get reverted ?
(In reply to Frank Griffin from comment #24) > And now, overnight with lid closed, powered down again. Did something get > reverted ? No, nothing got reverted. Run 'lsinitrd -m'. Does that list the "resume" module. If so, what you are seeing is not related to this bug, and you need to check your system logs to find out why the suspend/resume didn't work.
You're right, this appears to have nothing to do with dracut. Before the shutdown, the log has a flood of messages like this: Mar 18 23:34:57 jaglap2 kernel: rtw_8821ce 0000:02:00.0: [ 0] RxErr (First) Mar 18 23:34:57 jaglap2 kernel: pcieport 0000:00:1c.3: AER: Multiple Corrected error received: 0000:02:00.0 Mar 18 23:34:57 jaglap2 kernel: rtw_8821ce 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Mar 18 23:34:57 jaglap2 kernel: rtw_8821ce 0000:02:00.0: device [10ec:c821] error status/mask=00000001/0000e000 Mar 18 23:34:57 jaglap2 kernel: rtw_8821ce 0000:02:00.0: [ 0] RxErr (First) Mar 18 23:34:57 jaglap2 kernel: pcieport 0000:00:1c.3: AER: Multiple Corrected error received: 0000:02:00.0 Mar 18 23:34:57 jaglap2 kernel: rtw_8821ce 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Mar 18 23:34:57 jaglap2 kernel: rtw_8821ce 0000:02:00.0: device [10ec:c821] error status/mask=00000001/0000e000 Mar 18 23:34:57 jaglap2 kernel: rtw_8821ce 0000:02:00.0: [ 0] RxErr (First) I'm guessing a hardware problem with the wireless.
can be hw not coping with pcie aspm you can try on kernel command line: pcie_aspm=off
Thanks, Thomas. The log didn't indicate any reason for the poweroff, so I'm guessing that the flood of log messages hit some threshold, and based on googling I added "pci=noaer" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, which seems to have eliminated the flood. Can you tell me exactly which file and line corresponds to the kernel command line ?
Using pci=noaer suppresses the error messages caused by the "PCIe Bus Error". pcie_aspm=off and/or pcie_port_pm=off may stop the correctable errors from happening.
Thanks Dave, I figured that as well, but where do I put them ?
Assuming grub2 or grub2-efi, /etc/default/grub in the line starting with GRUB_CMDLINE_LINUX_DEFAULT= Run update-grub after adding the options to the string in that line.
I should have added, instead of editing the file directly, you can also choose to use "mcc/Boot/Setup boot system", select "Next" on the first screen, add the options in the "Append" field (space between each option, not a comma). It will run update-grub when "Finish" is selected.
This issue is relevant in Mageia 9 too. Including workaround in /etc/dracut.conf.d/51-mageia-resume.conf.
Changing this to a Mageia 9 bug, because of comment 33.
Version: 8 => 9
(In reply to Luděk Janča from comment #33) > This issue is relevant in Mageia 9 too. Including workaround in > /etc/dracut.conf.d/51-mageia-resume.conf. Please 1. Remove the workaround. 2. Provide the output of cat /proc/cmdline 3. Provide the output from running (as root) dracut -f
That's weird. I deleted row "add_dracutmodules...", ran dracut -fv and hibernation still works
Created attachment 13962 [details] dracut and cmdline
(In reply to Luděk Janča from comment #36) > That's weird. I deleted row "add_dracutmodules...", ran dracut -fv and > hibernation still works That's because I fixed dracut in cauldron before Mageia 9 was released (see comment 21).
Whiteboard: MGA8TOO => (none)Version: 9 => 8Status comment: (none) => Fixed in Mageia 9
(In reply to Martin Whitaker from comment #38) > (In reply to Luděk Janča from comment #36) > > That's weird. I deleted row "add_dracutmodules...", ran dracut -fv and > > hibernation still works > > That's because I fixed dracut in cauldron before Mageia 9 was released (see > comment 21). But as I mentioned in comment 33, hibernation did not work for me after a fresh install of Mageia 9. In a few weeks, I'm going to test fresh install again. In another laptop.
Resuming from hibernation doesn't work on my HP Pavilion 15 either, but with different symptoms. For me, it "resumes" to an unresponsive black screen, with using the power button to reboot the only choice to bring it back. Resuming from "sleep" works perfectly. That doesn't exactly fit this bug, but I don't know which of the many suspend/hibernate/hybrid/resume bugs it belongs in.
Result of my test: After fresh install of Mageia 9 hibernation doesn't work. But, if I run command `dracut -fv` (without any modification of anything), hibernation starts to work.
(In reply to Luděk Janča from comment #41) > Result of my test: > > After fresh install of Mageia 9 hibernation doesn't work. But, if I run > command `dracut -fv` (without any modification of anything), hibernation > starts to work. I confirm Luděk's purpose.
CC: (none) => dbitouze
(In reply to Thomas Andrews from comment #34) > Changing this to a Mageia 9 bug, because of comment 33. So for errata 9 then. Interesting find in Comment 41 - 42
Keywords: (none) => FOR_ERRATA9
Status comment: Fixed in Mageia 9 => (none)
Per https://forums.mageia.org/en/viewtopic.php?t=15110 still valid and fix in errata 8 works, so propagated to mga9 errata, shortened per Comment 41-42.
Keywords: FOR_ERRATA9 => IN_ERRATA9Version: 8 => 9Whiteboard: (none) => MGA8TOO
Per discussion in forum the original problem in this bug is fixed. There must be another bug that user action in comment 41 & 42 remedies. Updated the errata thus. https://wiki.mageia.org/en/Mageia_9_Errata#Hibernation
Resolution: (none) => FIXEDKeywords: IN_ERRATA9 => (none)Status: NEW => RESOLVED