mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: LetsDank <ichi2209@icloud.com>
To: Hamza Mahfooz <someguy@effective-light.com>
Cc: Leo Li <sunpeng.li@amd.com>,
	Mario Limonciello <superm1@kernel.org>,
	 Harry Wentland <harry.wentland@amd.com>,
	amd-gfx@lists.freedesktop.org,  dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] drm/amd/display: add DMU timeout recovery support
Date: Fri, 17 Jul 2026 19:44:16 +0300	[thread overview]
Message-ID: <178430665622.817433.2413622287692814812.gfxhub-stable-followup@icloud.com> (raw)
In-Reply-To: <178429570497.694276.1089609041510474786.dmub-recovery-v6-test@icloud.com>

Hi,

An important follow-up arrived shortly after my previous message.

The same separate gfxhub failure has now reproduced on the Fedora
7.1.3-200 kernel with amdgpu.dcdebugmask=0x810, after about 30.5 hours of
uptime. The sequence was:

  [gfxhub] page fault, process Xorg, ring 24, vmid 5
  GCVM_L2_PROTECTION_FAULT_STATUS: 0x00501031
  Faulty UTCL2 client ID: TCP
  PERMISSION_FAULTS: 0x3
  ring gfx_0.0.0 timeout
  Ring gfx_0.0.0 reset succeeded

Mesa then aborted Xorg in amdgpu_ctx_set_sw_reset_status(), ending the
X11 session and returning to SDDM. As in the v7.2-rc3 incident, there
were no DMUB, DMCUB, flip_done, or commit-wait timeout messages.

I captured a second complete 5.4 MB AMDGPU devcoredump. The fault status,
client, Xorg context, Mesa abort path, and ring-reset sequence match the
v7.2-rc3 incident.

This corrects any impression that the machine is stable against all GPU
faults with dcdebugmask=0x810. The workaround still appears to avoid the
original DMCUB/page-flip timeout signature, but it does not prevent this
separate gfxhub VM fault. The reproduction on both kernels also makes it
unlikely that the gfxhub fault was introduced by this patch series.

Both devcoredumps and the matching kernel logs are available if useful.

Regards,
LetsDank


  reply	other threads:[~2026-07-17 16:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 18:20 [PATCH v6 1/2] drm/atomic: attempt full modeset on page flip timeout Hamza Mahfooz
2026-05-05 18:20 ` [PATCH v6 2/2] drm/amd/display: add DMU timeout recovery support Hamza Mahfooz
2026-05-05 18:31   ` Mario Limonciello
2026-05-06 17:36   ` Hamza Mahfooz
2026-05-06 19:31     ` Leo Li
2026-07-17 13:41   ` LetsDank
2026-07-17 16:44     ` LetsDank [this message]
2026-05-05 18:31 ` [PATCH v6 1/2] drm/atomic: attempt full modeset on page flip timeout Mario Limonciello
2026-05-06 18:47 ` Ville Syrjälä
2026-05-07  0:22   ` Hamza Mahfooz

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=178430665622.817433.2413622287692814812.gfxhub-stable-followup@icloud.com \
    --to=ichi2209@icloud.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=someguy@effective-light.com \
    --cc=sunpeng.li@amd.com \
    --cc=superm1@kernel.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