Freeze after wake from suspend

Ask Fedora
, ,
2

  1. Do you have the problem as well when you boot with 5.19.6 and 5.19.4 ? You should have both in your grub menu at booting.
    → If the issue does not appear on 5.19.6, you can consider to stick with 5.19.6 until there is a new release. So, “jump over” 5.19.7 → the update from 5.19.6 to 5.19.7 is not security critical, and it is likely that there will be acpi-relevant changes in the next kernel.

  2. What is the output of cat /proc/sys/kernel/tainted ? This tells us if there are modifications on your kernel. The output is just a number. An unmodified kernel is 0.

  3. What is the output of lsmod | grep asus ? I would like to exclude that this is linked to the current issue we have with an asus module that is not yet fixed but will be soon. If that will be the case, we have a workaround for that, but let’s check first.

→ if 5.19.6 works fine and if you are ok with waiting for the next kernel, or if “lsmod | grep asus” outputs anything, you can wait with the next steps and just let us know what you have so far. Otherwise:

  1. Create a boot that is only dedicated to create relevant logs. So, boot your 5.19.7 kernel and after booting, just log in, provoke the problem, and once your system got stuck, force reset and at the next boot, let us know the output of sudo journalctl --boot=-1 → this shows the logs of the last boot (which is then the affected boot). Feel free to randomize data if you consider something contained as private (e.g., MAC address, user name). Also, it would be helpful if you could let us know the very time when you suspended (that helps when reading the logs) and what exact symptoms you had at this occurrence.

  2. If you don’t mind installing inxi (it is contained in the default repo of Fedora), inxi -Fz would be valuable complementary information (“-F” = all system information, “-z” = keep private information hidden). Feel free to check if there is anything left you consider private, but let us know if you change the output of it.

  3. acpitool can be helpful to identify the exact device that causes the problem (if one specific device is responsible), which can help to identify a driver/module/code that could be changed/modified to solve the issue. So disabling them one by one (so, always just one disabled), and each time testing if the problem can be provoked. This might safe time.