From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221012] New: GPU page fault on AMD RX 7600 XT after commit bf2084a7b1d75d093b6a79df4c10142d49fbaa0e
Date: Mon, 26 Jan 2026 21:40:59 +0000 [thread overview]
Message-ID: <bug-221012-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221012
Bug ID: 221012
Summary: GPU page fault on AMD RX 7600 XT after commit
bf2084a7b1d75d093b6a79df4c10142d49fbaa0e
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: geschw@pm.me
Regression: No
Created attachment 309237
--> https://bugzilla.kernel.org/attachment.cgi?id=309237&action=edit
dmesg, lspci
GPU page fault occurs when running HIP/ROCm workloads on the AMD Radeon RX 7600
XT with kernel version 6.18.2. This issue is introduced by commit
bf2084a7b1d75d093b6a79df4c10142d49fbaa0e, which modifies the alignment logic
for split SVM ranges and introduces the use of huge pages. The error can be
resolved by reverting this commit.
The fault is reproducible under consistent workloads, and it prevents
successful execution of HIP-based tasks, such as PyTorch model training, on
this GPU. The error manifests as permission faults in the GPU driver logs.
--
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 reply other threads:[~2026-01-26 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 21:40 bugzilla-daemon [this message]
2026-01-26 23:27 ` [Bug 221012] GPU page fault on AMD RX 7600 XT after commit bf2084a7b1d75d093b6a79df4c10142d49fbaa0e bugzilla-daemon
2026-01-27 8:50 ` bugzilla-daemon
2026-01-27 11:11 ` bugzilla-daemon
2026-01-27 11:14 ` bugzilla-daemon
2026-01-27 11:20 ` 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-221012-2300@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.