From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 217916] New: amdgpu: ring gfx_low timeout (Google Maps zooming)
Date: Sat, 16 Sep 2023 04:24:39 +0000 [thread overview]
Message-ID: <bug-217916-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217916
Bug ID: 217916
Summary: amdgpu: ring gfx_low timeout (Google Maps zooming)
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: warren@togami.com
Regression: No
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout,
signaled seq=3002, emitted seq=3004
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process
chromium-browse pid 4034 thread chromium-b:cs0 pid 4074
kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset begin!
kernel: amdgpu 0000:05:00.0: amdgpu: MODE2 reset
kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset succeeded, trying to resume
Thinkpad T14s Gen 2 AMD
AMD Ryzen 7 PRO 5850U with Radeon Graphics
Fedora 38
mesa-23.1.7-1.fc38.x86_64
chromium-116.0.5845.187-1.fc38.x86_64
Working versions: kernel-6.4.16
Broken versions: kernel-6.5.2 and 6.5.3
Reproduce Procedure
1) Boot into kernel-6.5.2 or 6.5.3.
2) Run Chromium browser
3) maps.google.com
4) Search for an address. Plot a driving route.
5) Something about the map zooming causing the amdgpu crash. Sometimes it takes
2-3 attempts for the crash to occur.
It does not crash with kernel-6.4.x.
https://fedorapeople.org/~wtogami/a/2023/KERNEL-6.5.3-amdgpu-crash3.log
full dmesg log
--
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:[~2023-09-16 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 4:24 bugzilla-daemon [this message]
2023-09-16 8:15 ` [Bug 217916] amdgpu: ring gfx_low timeout (Google Maps zooming) 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-217916-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.