From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221040] AMD Ryzen 5700G (Renoir/Cezanne): Second suspend hangs after "PM: suspend entry (deep)" - xhci_hcd and asus_wmi LPS0 involvement
Date: Sat, 29 Aug 2026 15:54:14 +0000 [thread overview]
Message-ID: <bug-221040-2300-6UIfWMA3UI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221040-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221040
Bertram Ganz (s93nesua@bote.unbox.at) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|ANSWERED |CODE_FIX
--- Comment #5 from Bertram Ganz (s93nesua@bote.unbox.at) ---
Update: Issue appears resolved (kernel 6.18.42-1-lts / Mesa 26.0)
After several months of using hibernation (S4) as a workaround, I retested
suspend/resume (S3) today and completed 3 consecutive cycles successfully
with no hang - previously the second cycle would reliably hang after
"PM: suspend entry (deep)" with no further kernel output, requiring a hard
reset.
Version delta:
My original report was on:
- Kernel: 6.12.63-1-lts
- Mesa: 25.3.4
I retested a few months ago on 6.18.17-1-lts and it was still failing at
that point (see earlier comments). Just retested again on:
- Kernel: 6.18.42-1-lts
- Mesa: 26.0
...and suspend/resume now works reliably. So the fix landed somewhere
between 6.18.17 and 6.18.42 (kernel), or possibly required the Mesa 26.0
upgrade in combination - I can't pinpoint the exact patch given the size
of the jump.
Still present (but non-fatal):
These log messages still appear but no longer block suspend/resume:
gnome-shell: Cursor update failed: drmModeAtomicCommit: Invalid argument
xhci_hcd 0000:01:00.0: xHC error in resume, USBSTS 0x401, Reinit
asus_wmi: failed to register LPS0 sleep handler in asus-wmi
Hardware:
- AMD Ryzen 7 5700G (Renoir/Cezanne)
- ASUS ROG STRIX B450-I GAMING (BIOS 5901)
- amdgpu.dcfeaturemask parameter removed, no longer needed
Status:
I'll leave this open for now since I haven't pinpointed the exact fix, and
the underlying error messages are still present even though non-fatal.
Feel free to close if this is considered sufficiently resolved, or let me
know if a bisect would help.
Also posted updates on:
- AMD GitLab: https://gitlab.freedesktop.org/drm/amd/-/issues/4927
- EndeavourOS forum:
https://forum.endeavouros.com/t/amd-ryzen-5700g-renoir-asus-b450-i-second-suspend-hangs-after-resume-xhci-hcd-asus-wmi-issues/77923
- r/AMDHelp:
https://www.reddit.com/r/AMDHelp/comments/1qv40fo/amd_ryzen_5700g_renoir_asus_b450i_second_suspend/
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-08-29 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 19:58 [Bug 221040] New: AMD Ryzen 5700G (Renoir/Cezanne): Second suspend hangs after "PM: suspend entry (deep)" - xhci_hcd and asus_wmi LPS0 involvement bugzilla-daemon
2026-02-03 20:00 ` [Bug 221040] " bugzilla-daemon
2026-02-03 20:07 ` bugzilla-daemon
2026-02-03 21:02 ` bugzilla-daemon
2026-02-04 8:38 ` bugzilla-daemon
2026-08-29 15:54 ` bugzilla-daemon [this message]
2026-08-29 15:57 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221040-2300-6UIfWMA3UI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox