dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 219492] amdgpu: failed to write reg 28b4 wait reg 28c6 and amdgpu: failed to write reg 1a6f4 wait reg 1a706
Date: Wed, 19 Aug 2026 11:26:29 +0000	[thread overview]
Message-ID: <bug-219492-2300-1wRrnkUF3G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219492-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219492

Denis Pisarev (pisarevden+bugzilla@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pisarevden+bugzilla@gmail.c
                   |                            |om

--- Comment #5 from Denis Pisarev (pisarevden+bugzilla@gmail.com) ---
"failed to write reg 28b4 wait reg 28c6" persists for hours after every S4
(hibernate) resume, Cezanne, kernel 7.1.8

Adding another reproduction on a different setup (desktop use, no ROCm),
with two observations that go beyond the original report:

1. The failures are NOT limited to early resume. They continue
   indefinitely (80-140 per hour for 9+ hours) until reboot.
2. On this machine there are no "TLB flush failed for PASID" lines at
   all - only the two reg write/wait pairs.

HARDWARE / ENVIRONMENT
----------------------
CPU:     AMD Ryzen 7 PRO 5850U
GPU:     AMD Cezanne iGPU [1002:1638] (rev d1), amdgpu, DMUB 0x0101002B
Kernel:  7.1.8-1-MANJARO
Desktop: KDE Plasma / KWin Wayland, no ROCm or compute workloads
Trigger: resume from hibernation (S4), 100% reproducible over multiple
         cycles across two days; does not occur on a fresh boot

LOG EXCERPT (resume at Aug 19 10:52:39)
---------------------------------------
Aug 19 10:52:39 horsehead kernel: Freezing remaining freezable tasks completed
(elapsed 0.001 seconds)
Aug 19 10:52:39 horsehead kernel: amdgpu 0000:07:00.0: failed to write reg 28b4
wait reg 28c6
Aug 19 10:52:39 horsehead kernel: amdgpu 0000:07:00.0: failed to write reg
1a6f4 wait reg 1a706
Aug 19 10:52:39 horsehead kernel: amdgpu 0000:07:00.0: failed to write reg 28b4
wait reg 28c6
Aug 19 10:52:39 horsehead kernel: amdgpu 0000:07:00.0: failed to write reg
1a6f4 wait reg 1a706
Aug 19 10:52:39 horsehead systemd-sleep[1062034]: System returned from sleep
operation 'hibernate'.

The first failures appear in the same second as the thaw, interleaved
with the hibernation-exit messages. On an earlier cycle the resume also
produced:

Aug 18 10:04:42 horsehead kernel: amdgpu 0000:07:00.0: MODE2 reset
Aug 18 10:04:42 horsehead kernel: usb usb5: root hub lost power or was reset
(... usb6, usb7, usb1 ...)

ONGOING RATE AFTER RESUME (Aug 19, single cycle)
------------------------------------------------
hour 10 (resume 10:52): 138 errors
hour 11:               140 errors
hour 12:                78 errors (still ongoing at time of writing)
Previous cycle (Aug 18, resumed 10:04): 1414 errors over the day,
still occurring 9+ hours later. No "TLB flush failed for PASID"
messages appear on this machine, only the 28b4/28c6 and 1a6f4/1a706
pairs, always together.

USER-VISIBLE IMPACT
-------------------
The retry path makes the whole desktop sluggish (stalls in the
compositor and apps). CPU and memory are idle; the disk is not involved
(NVMe <2% busy, fsync latency normal), yet PSI "some" io pressure reads
~80% because tasks spend their time sleeping in the retry loop.

WORKAROUND
----------
Reboot clears it until the next S4 resume. Using suspend-to-RAM avoids
triggering it (S4 is the only trigger observed).

NOTE
---------------
the resume_gpu_stable proposal from January
(https://lore.kernel.org/amd-gfx/20260106125929.25214-6-sunlightlinux@gmail.com/)
was rejected because it disabled the KIQ path permanently, but the
persistent-hours-long failure pattern seen here suggests KIQ does not
recover on its own after S4 resume on gmc_v9 + Cezanne - at least not
under a plain Wayland desktop workload.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-08-19 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12  7:16 [Bug 219492] New: amdgpu: failed to write reg 28b4 wait reg 28c6 and amdgpu: failed to write reg 1a6f4 wait reg 1a706 bugzilla-daemon
2024-11-12  7:18 ` [Bug 219492] " bugzilla-daemon
2024-11-12 11:06 ` bugzilla-daemon
2025-02-10 19:01 ` bugzilla-daemon
2025-06-05  7:11 ` bugzilla-daemon
2025-06-24  6:08 ` bugzilla-daemon
2026-08-19 11:26 ` bugzilla-daemon [this message]

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-219492-2300-1wRrnkUF3G@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