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: Mon, 12 Sep 2022 17:07:07 +0000 [thread overview]
Message-ID: <bug-213145-2300-MyYoIzFsls@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213145-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213145
nvaert1986 (nvaert1986@hotmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nvaert1986@hotmail.com
--- Comment #21 from nvaert1986 (nvaert1986@hotmail.com) ---
I'm experiencing the same issue on 5.19 with mesa. It rarely happens, but when
it happens my whole system needs a reboot. I've seen it happening with Firefox
and Steam so far.
[drm:0xffffffffc04e61a6] *ERROR* Waiting for fences timed out!
[drm:0xffffffffc04e61a6] *ERROR* Waiting for fences timed out!
[drm:0xffffffffc0465370] *ERROR* Process information: process firefox pid 1918
thread firefox:cs0 pid 2069
amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
amdgpu 0000:03:00.0: [drm:0xffffffffc0321d49] *ERROR* ring kiq_2.1.0 test
failed (-110)
[drm:0xffffffffc03b4bfc] *ERROR* KGQ disable failed
[drm:0xffffffffc03b4a60] *ERROR* failed to halt cp gfx
[drm] free PSP TMR buffer
DMAR: DRHD: handling fault status reg 3
DMAR: [DMA Read NO_PASID] Request device [03:00.0] fault addr 0x77d0541a000
[fault reason 0x04] Access beyond MGAW
DMAR: DRHD: handling fault status reg 3
DMAR: [DMA Read NO_PASID] Request device [03:00.0] fault addr 0x77d0541e000
[fault reason 0x04] Access beyond MGAW
CPU: 0 PID: 1028 Comm: kworker/u48:22 Tainted: G O 5.19.1
Hardware name: Micro-Star International Co., Ltd. MS-7D31/MPG Z690 EDGE WIFI
DDR4 (MS-7D31), BIOS 1.40 05/18/2022
Workqueue: amdgpu-reset-dev 0xffffffffc0242a90
Call Trace:
<TASK>
0xffffffffa28f2514
0xffffffffc065e673
0xffffffffc065ef99
0xffffffffc04653ca
0xffffffffc0242aeb
0xffffffffa1f30ae8amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
0xffffffffa1f31048
? 0xffffffffa1f31000
0xffffffffa1f372fa
? 0xffffffffa1f37220
0xffffffffa1e010ef
</TASK>
amdgpu 0000:03:00.0: amdgpu: MODE1 reset
amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
[drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
[drm] VRAM is lost due to GPU reset!
[drm] PSP is resuming...
Here it initializes my full GPU, but then throws:
[drm] Skip scheduling IBs!
and the crash starts over again.
--
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-09-12 17:07 UTC|newest]
Thread overview: 36+ 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 [this message]
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
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
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-MyYoIzFsls@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).