Description of problem: when I upgraded my computer (not used in a long time) it started to crash at sleep/resume. I installed older kernels and could track the problem: 5.12.15 is OK, while 5.13.12 and next ones fail. Version-Release number of selected component (if applicable): >= kernel-desktop-5.13.12-2.mga8-1-1.mga8 How reproducible: put to sleep: the computer crashes. Steps to Reproduce: 1. 2. 3.
Created attachment 13592 [details] 5.12.15 journal
Created attachment 13593 [details] 5.13.12 journal it crashes just after the line: kernel: PM: suspend entry (deep)
Created attachment 13594 [details] 5.12.15 journal - crash Well, it also crashed with 5.12.15 :( MAybe this is something else after all. Testing on older kernels, repeated slppe/resume to see if it is ok.
It seems that you lack behind many updates and you only test with really old kernels. Did you already do a complete update of the system to an actual and supported kernel-5.15.x branch and tested that?
The system is an up to date mga8 and I tested with all the kernel from 5.10 up to 6.0.12, and as sleep has worked with 5.10, I made a dichotomy to find which kernel was ok, but at the end I don't get reliable results... E.g. just now 5.10 put it to sleep (I can hear the HD stop for example), but it crashed while waking up (black screen with unresponsive mouse pointer).
All that seems thorough. Hopefully to expedite journal perusal, here are summaries of the vital parts. (In reply to Jean-Christophe Cardot from comment #1) > Created attachment 13592 [details] > 5.12.15 journal [NO crash] déc. 26 12:27:07 localhost systemd[1]: Reached target Sleep. ░░ Subject: L'unité (unit) sleep.target a terminé son démarrage ░░ Defined-By: systemd ░░ L'unité (unit) sleep.target a terminé son démarrage, avec le résultat done. déc. 26 12:27:07 localhost systemd[1]: Starting Suspend... ░░ Subject: L'unité (unit) systemd-suspend.service a commencé à démarrer ░░ Defined-By: systemd ░░ L'unité (unit) systemd-suspend.service a commencé à démarrer. déc. 26 12:27:07 localhost systemd-sleep[10977]: Suspending system... ░░ Subject: Le système entre dans l'état de repos (sleep state) suspend ░░ Defined-By: systemd ░░ Le système est maintenant à l'état de repos (sleep state) suspend. déc. 26 12:27:07 localhost kernel: PM: suspend entry (deep) ... déc. 26 12:28:00 localhost kernel: ACPI: Preparing to enter system sleep state S3 ... déc. 26 12:28:00 localhost kernel: ACPI: Low-level resume complete ... déc. 26 12:28:00 localhost kernel: ACPI: Waking up from system sleep state S3 et seq (In reply to Jean-Christophe Cardot from comment #2) > Created attachment 13593 [details] > 5.13.12 journal [crash] > it crashes just after the line: > kernel: PM: suspend entry (deep) déc. 26 12:38:00 localhost systemd[1]: Reached target Sleep. ░░ Subject: L'unité (unit) sleep.target a terminé son démarrage ░░ Defined-By: systemd ░░ L'unité (unit) sleep.target a terminé son démarrage, avec le résultat done. déc. 26 12:38:00 localhost systemd[1]: Starting Suspend... ░░ Subject: L'unité (unit) systemd-suspend.service a commencé à démarrer ░░ Defined-By: systemd ░░ L'unité (unit) systemd-suspend.service a commencé à démarrer. déc. 26 12:38:00 localhost systemd-sleep[19943]: Suspending system... ░░ Subject: Le système entre dans l'état de repos (sleep state) suspend ░░ Defined-By: systemd ░░ Le système est maintenant à l'état de repos (sleep state) suspend. déc. 26 12:38:00 localhost kernel: PM: suspend entry (deep) !!! (In reply to Jean-Christophe Cardot from comment #3) > Created attachment 13594 [details] > 5.12.15 journal - crash > Well, it also crashed with 5.12.15 :( Identical to the crash sequence above. There are several bugs about suspend/resume not working for specific users. Assigning to kernel initially.
Assignee: bugsquad => kernel
Just had time to test woth a MGA6 live usb, kernel 4.14.70-desktop-2.mga6 Suspend/resume works. I guess I would have to bissect between this version and 5.10. Won't be fast though...