From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221089] New: amdgpu: Regression in Linux 7.0 with RX-580: BUG: unable to handle page fault for address: fffffffffffffff1
Date: Fri, 13 Feb 2026 03:17:25 +0000 [thread overview]
Message-ID: <bug-221089-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221089
Bug ID: 221089
Summary: amdgpu: Regression in Linux 7.0 with RX-580: BUG:
unable to handle page fault for address:
fffffffffffffff1
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: pinkflames.linux@gmail.com
Regression: Yes
Bisected ba448f9ed62cf5a89603a738e6de91fc6c42ab35
commit-id:
With my particular setup commit ba448f9ed62cf5a89603a738e6de91fc6c42ab35 causes
the plasma-login-manager 6.6 Beta 2 (a.k.a. version 6.5.91) to only show a
black screen with mouse cursor stuck in the middle of the screen (default
position).
After booting into a known working kernel, the journald of the failed boot
indicates that the amdgpu driver segfaulted after the login manager started.
I'll append a kernel stack trace to this bug report in a moment.
As part of bisecting and then digging into this I also tried a non-RT kernel as
well as manually setting `gpu_sched.sched_policy=1` which should correspond to
the deadline GPU scheduler instead of the `gpu_sched.sched_policy=0` that I
usually set (and which, I believe, set the RR scheduler). However the only fix
I found was to revert the commit, which is what I'm now running on top of
current git master (commit 7449f86bafcdb588422bb14a4babfd285e723670).
All crashes seem very similar with the only difference being that the one
non-RT build I tested lacked the `? dc_stream_get_scanoutpos+0x116/0x140
[amdgpu]` line but otherwise they all look the same to my pleb eyes.
I tried CC'ing the relevant people but seems their AMD addresses are not known
to the kernel infrastructure
--
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-02-13 3:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 3:17 bugzilla-daemon [this message]
2026-02-13 3:20 ` [Bug 221089] amdgpu: Regression in Linux 7.0 with RX-580: BUG: unable to handle page fault for address: fffffffffffffff1 bugzilla-daemon
2026-02-13 3:23 ` bugzilla-daemon
2026-02-13 7:06 ` bugzilla-daemon
2026-02-13 14:58 ` bugzilla-daemon
2026-02-13 17:41 ` bugzilla-daemon
2026-02-13 17:48 ` bugzilla-daemon
2026-02-16 7:25 ` bugzilla-daemon
2026-02-16 9:20 ` bugzilla-daemon
2026-02-16 10:24 ` 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-221089-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.