From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"
Date: Sat, 12 Nov 2022 16:24:21 +0000 [thread overview]
Message-ID: <bug-213145-2300-wWErLALaxN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213145-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213145
fmhirtz@maunet.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fmhirtz@maunet.org
--- Comment #28 from fmhirtz@maunet.org ---
I'm seeing what appears to be this on Fedora 37 with an AMD 5700xt. Normal
desktop use in Wayland/Gnome will sporadically freeze and crash every couple of
days. It normally will reset back to the login given some time:
Kernel: 6.0.7-301.fc37.x86_64
Mesa: mesa-*23.0.0-0.3.git74bbeb5.fc37
~~~
Nov 08 02:01:33 workstation kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]]
*ERROR* Waiting for fences timed out!
Nov 08 02:01:33 workstation kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring gfx_0.0.0 timeout, signaled seq=14613616, emitted seq=14613618
Nov 08 02:01:33 workstation kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process firefox pid 21845 thread firefox:cs0 pid 21922
Nov 08 02:01:33 workstation kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset
begin!
Nov 08 02:01:34 workstation kernel: amdgpu 0000:0c:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed
(-110)
Nov 08 02:01:34 workstation kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR*
KGQ disable failed
Nov 08 02:01:34 workstation kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR*
failed to halt cp gfx
Nov 08 02:01:34 workstation kernel: [drm] free PSP TMR buffer
Nov 08 02:01:34 workstation kernel: CPU: 19 PID: 871009 Comm: kworker/u64:3 Not
tainted 5.19.16-301.fc37.x86_64 #1
Nov 08 02:01:34 workstation kernel: Hardware name: MicroElectronics G464/TUF
GAMING X570-PLUS (WI-FI), BIOS 3001 12/04/2020
Nov 08 02:01:34 workstation kernel: Workqueue: amdgpu-reset-dev
drm_sched_job_timedout [gpu_sched]
Nov 08 02:01:34 workstation kernel: Call Trace:
Nov 08 02:01:34 workstation kernel: <TASK>
Nov 08 02:01:34 workstation kernel: dump_stack_lvl+0x44/0x5c
Nov 08 02:01:34 workstation kernel: amdgpu_do_asic_reset+0x26/0x459 [amdgpu]
Nov 08 02:01:34 workstation kernel:
amdgpu_device_gpu_recover_imp.cold+0x59d/0x8cb [amdgpu]
Nov 08 02:01:34 workstation kernel: amdgpu_job_timedout+0x156/0x190 [amdgpu]
Nov 08 02:01:34 workstation kernel: ? __switch_to+0x106/0x430
Nov 08 02:01:34 workstation kernel: drm_sched_job_timedout+0x76/0x110
[gpu_sched]
Nov 08 02:01:34 workstation kernel: process_one_work+0x1c7/0x380
Nov 08 02:01:34 workstation kernel: worker_thread+0x4d/0x380
Nov 08 02:01:34 workstation kernel: ? _raw_spin_lock_irqsave+0x23/0x50
Nov 08 02:01:34 workstation kernel: ? process_one_work+0x380/0x380
Nov 08 02:01:34 workstation kernel: kthread+0xe9/0x110
Nov 08 02:01:34 workstation kernel: ? kthread_complete_and_exit+0x20/0x20
Nov 08 02:01:34 workstation kernel: ret_from_fork+0x22/0x30
Nov 08 02:01:34 workstation kernel: </TASK>
Nov 08 02:01:34 workstation kernel: amdgpu 0000:0c:00.0: amdgpu: BACO reset
Nov 08 02:01:37 workstation kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset
succeeded, trying to resume
Nov 08 02:01:37 workstation kernel: [drm] PCIE GART of 512M enabled (table at
0x0000008000300000).
Nov 08 02:01:37 workstation kernel: [drm] VRAM is lost due to GPU reset!
Nov 08 02:01:37 workstation kernel: [drm] PSP is resuming...
Nov 08 02:01:37 workstation kernel: [drm] reserve 0x900000 from 0x81fe600000
for PSP TMR
...
~~~
--
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 prev parent reply other threads:[~2022-11-12 16:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 14:46 [Bug 213145] New: AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!" bugzilla-daemon
2021-05-19 14:47 ` [Bug 213145] " bugzilla-daemon
2021-05-19 14:47 ` bugzilla-daemon
2021-05-27 13:43 ` bugzilla-daemon
2021-06-04 21:37 ` bugzilla-daemon
2021-06-04 21:38 ` bugzilla-daemon
2021-06-05 0:38 ` bugzilla-daemon
2021-06-07 19:37 ` bugzilla-daemon
2021-06-07 19:41 ` bugzilla-daemon
2021-06-08 16:38 ` bugzilla-daemon
2021-06-08 17:17 ` bugzilla-daemon
2021-06-08 17:25 ` bugzilla-daemon
2021-06-08 17:30 ` bugzilla-daemon
2022-05-25 2:21 ` bugzilla-daemon
2022-05-25 2:30 ` bugzilla-daemon
2022-05-25 4:03 ` bugzilla-daemon
2022-05-25 4:07 ` bugzilla-daemon
2022-05-25 20:18 ` bugzilla-daemon
2022-05-29 7:40 ` bugzilla-daemon
2022-05-31 19:59 ` bugzilla-daemon
2022-06-13 6:58 ` bugzilla-daemon
2022-07-26 20:42 ` bugzilla-daemon
2022-09-12 17:07 ` bugzilla-daemon
2022-09-30 15:00 ` bugzilla-daemon
2022-10-09 20:11 ` bugzilla-daemon
2022-10-10 18:24 ` bugzilla-daemon
2022-10-12 10:51 ` bugzilla-daemon
2022-10-12 12:01 ` bugzilla-daemon
2022-10-30 16:57 ` bugzilla-daemon
2022-11-12 16:24 ` bugzilla-daemon [this message]
2022-11-20 21:57 ` bugzilla-daemon
2022-11-26 20:19 ` bugzilla-daemon
2023-07-01 5:25 ` bugzilla-daemon
2023-07-01 5:27 ` bugzilla-daemon
2024-01-04 11:33 ` bugzilla-daemon
2024-02-04 0:04 ` bugzilla-daemon
2025-02-10 10:57 ` bugzilla-daemon
2025-02-10 12:37 ` 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-213145-2300-wWErLALaxN@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