From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 220640] New: Hardware: - GPU: AMD Radeon RX 6600 / 6600 XT / 6600M (Navi 23) - Subsystem: XFX Limited [1eae:6505] - Kernel driver: amdgpu - Kernel: 6.14.0-33-generic - OS: Ubuntu 24.04 (upstream testing) Issue: During normal usage in GNOME, the GPU occasionally loses
Date: Wed, 08 Oct 2025 06:11:43 +0000 [thread overview]
Message-ID: <bug-220640-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220640
Bug ID: 220640
Summary: Hardware: - GPU: AMD Radeon RX 6600 / 6600 XT / 6600M
(Navi 23) - Subsystem: XFX Limited [1eae:6505] -
Kernel driver: amdgpu - Kernel: 6.14.0-33-generic -
OS: Ubuntu 24.04 (upstream testing) Issue: During
normal usage in GNOME, the GPU occasionally loses
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: etkinator@gmail.com
Regression: No
Created attachment 308775
--> https://bugzilla.kernel.org/attachment.cgi?id=308775&action=edit
kernel logs showing context lost events, GPU resets, and SMU/PSP messages.
Hardware:
- GPU: AMD Radeon RX 6600 / 6600 XT / 6600M (Navi 23)
- Subsystem: XFX Limited [1eae:6505]
- Kernel driver: amdgpu
- Kernel: 6.14.0-33-generic
- OS: Ubuntu 24.04 (upstream testing)
Issue:
During normal usage in GNOME, the GPU occasionally loses context, resulting in
visible system issues:
- White, sometimes noisy, screen (GPU output frozen)
- System freeze / unresponsive graphical session
- GPU reset occurs automatically
- Kernel log shows:
amdgpu: The CS has cancelled because the context is lost. This context is
innocent.
amdgpu 0000:09:00.0: GPU reset(2) succeeded!
BACO (Bus Active/Chip Off) for runtime power management is enabled.
Logs indicate repeated SMU / PSP resume sequences and GPU mode resets:
amdgpu 0000:09:00.0: Using BACO for runtime pm
amdgpu 0000:09:00.0: SMU is resumed successfully!
Steps to reproduce:
1. Boot Ubuntu 24.04 with kernel 6.14.0-33-generic.
2. Use system normally (GNOME shell active).
3. Intermittently, observe:
- White / noisy screen
- GPU reset in kernel logs
- Temporary freeze of graphical session
Additional info:
- SMU driver interface version does not match firmware (driver 0x0f, fw 0x13),
but GPU resumes.
- GPU operates normally after reset.
- BACO active for runtime PM.
Impact:
- System instability: freezes, temporary loss of graphical output.
- Potential interference with GPU workloads.
- Annoying / disruptive for desktop usage.
Request:
- Investigate root cause of context loss leading to visible screen corruption.
- Verify interaction with BACO power management.
- Advise on firmware/driver fixes or workarounds.
--
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:[~2025-10-08 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 6:11 bugzilla-daemon [this message]
2025-10-08 15:52 ` [Bug 220640] Hardware: - GPU: AMD Radeon RX 6600 / 6600 XT / 6600M (Navi 23) - Subsystem: XFX Limited [1eae:6505] - Kernel driver: amdgpu - Kernel: 6.14.0-33-generic - OS: Ubuntu 24.04 (upstream testing) Issue: During normal usage in GNOME, the GPU occasionally loses 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-220640-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).