Bug 219632 - Failure to resume, video and user mode stuck, Magic-SysRQ works
Summary: Failure to resume, video and user mode stuck, Magic-SysRQ works
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: AMD Linux
: P3 high
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-25 16:30 UTC by Eduard Bloch
Modified: 2024-12-28 12:49 UTC (History)
0 users

See Also:
Kernel Version: 6.11.0, 6.12.6
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg-from-journalctl (147.58 KB, text/plain)
2024-12-25 16:30 UTC, Eduard Bloch
Details
devices (56.17 KB, text/plain)
2024-12-25 16:31 UTC, Eduard Bloch
Details

Description Eduard Bloch 2024-12-25 16:30:55 UTC
Created attachment 307405 [details]
dmesg-from-journalctl

Hello,

situation here:

- Kernel: 6.12.6 (issue also reproducible with 6.12.3 and also random 6.11.x versions)
- Mainboard: MSI B550M-PRO-VDH-WIFI, replaced a few months ago
- CPU: AMD Ryzen 5700G
- Video: Radeon RX 6700G

The combo has been working fine with kernels 6.9.x, 6.10.x, including regular suspend/resume cycles (S3). I noticed first trouble when testing 6.11-rcX versions. It failed to resume but sometimes only on the second or third suspend cycle. The obvious symptoms were that system powered up but video never came back, neither did the onboard NIC, although USB keyboard was still responsive and I could sync and restart via Magic-SysRQ combos. No journalctl logs were shown, so I guess that userspace never has been resumed.

I have tried the CONFIG_PM_TRACE / CONFIG_PM_DEBUG method already. No usable data reported from there, i.e. from dmesg:

Dez 25 16:11:46 zombie kernel: PM: RTC time: 15:11:30, date: 2024-12-25
...
Dez 25 16:11:46 zombie kernel: PM:   Magic number: 4:125:185

$ cat /sys/power/pm_trace_dev_match
usb
acpi-wmi
acpi

I wanted to be helpful and have tried the bisecting already. That is leading to nowhere, I have given up after some hours. Because some builds are not showing the same behavior, i.e. the repro runs eventually end up in strange behavior with non-responsive USB keyboard (either not lighted at all or blinking leds on key strokes but not doing anything). And skipping those bisect steps means that it keeps jumping between 6.9.x and 6.11.x and 6.10.x branches, and I have no further ideas on how to continue.

On the other hand, 6.10.14 version is running perfectly right now, but IMHO that issue smells extremely and I am using regular&popular hardware parts, so it might affect lots of users with similar setups.
Comment 1 Eduard Bloch 2024-12-25 16:31:15 UTC
Created attachment 307406 [details]
devices
Comment 2 Eduard Bloch 2024-12-28 12:49:13 UTC
NOTE: this seems to be resolved in current master (6.13-rc4+), at least in the following commit. Not sure where the actual fix was introduced, probably in https://github.com/torvalds/linux/commit/af215c980c1fbf1ca01675b128b0dd194745b880 .

Note You need to log in before you can comment on or make changes to this bug.