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: Sun, 20 Nov 2022 21:57:52 +0000 [thread overview]
Message-ID: <bug-213145-2300-usxsIxzpfz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213145-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213145
Viktor (sgasgar@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sgasgar@gmail.com
--- Comment #29 from Viktor (sgasgar@gmail.com) ---
Same problem on Lenovo Thinkpad T14 Gen3 with Ryzen 7 and Radeon 680M.
Spontaneous freezes on kernels 5.17.* and 6.0.*.
Here is the log:
Nov 20 22:31:39 calculate kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
*ERROR* Waiting for fences timed out!
Nov 20 22:31:39 calculate kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring sdma0 timeout, signaled seq=146659, emitted seq=146661
Nov 20 22:31:39 calculate kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process pid 0 thread pid 0
Nov 20 22:31:39 calculate kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
Nov 20 22:31:39 calculate kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring gfx_0.0.0 timeout, signaled seq=986766, emitted seq=986766
Nov 20 22:31:39 calculate kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process X pid 4963 thread X:cs0 pid 5224
Nov 20 22:31:39 calculate kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
Nov 20 22:31:39 calculate kernel: amdgpu 0000:04:00.0: amdgpu: Bailing on TDR
for s_job:df2df, as another already in progress
Nov 20 22:31:40 calculate kernel: amdgpu 0000:04:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed
(-110)
Nov 20 22:31:40 calculate kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ
disable failed
Nov 20 22:31:40 calculate kernel: amdgpu 0000:04:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed
(-110)
Nov 20 22:31:40 calculate kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ
disable failed
Nov 20 22:31:40 calculate kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR*
failed to halt cp gfx
Nov 20 22:31:40 calculate kernel: [drm] free PSP TMR buffer
Nov 20 22:31:40 calculate kernel: amdgpu 0000:04:00.0: amdgpu: MODE2 reset
Nov 20 22:31:40 calculate kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset
succeeded, trying to resume
Nov 20 22:31:40 calculate kernel: [drm] PCIE GART of 512M enabled (table at
0x000000F4008C9000).
Nov 20 22:31:40 calculate kernel: [drm] PSP is resuming...
Nov 20 22:31:40 calculate kernel: [drm] reserve 0xa00000 from 0xf43f400000 for
PSP TMR
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional
ras ta ucode is not available
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional
rap ta ucode is not available
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY:
securedisplay ta ucode is not available
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: SMU is
resuming...
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed
successfully!
Nov 20 22:31:41 calculate kernel: [drm] DMUB hardware initialized:
version=0x0400001A
Nov 20 22:31:41 calculate kernel: [drm] kiq ring mec 2 pipe 1 q 0
Nov 20 22:31:41 calculate kernel: [drm] VCN decode and encode initialized
successfully(under DPG Mode).
Nov 20 22:31:41 calculate kernel: [drm] JPEG decode initialized successfully.
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0
uses VM inv eng 0 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0
uses VM inv eng 1 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0
uses VM inv eng 4 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0
uses VM inv eng 5 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0
uses VM inv eng 6 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1
uses VM inv eng 7 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1
uses VM inv eng 8 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1
uses VM inv eng 9 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1
uses VM inv eng 10 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0
uses VM inv eng 11 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses
VM inv eng 12 on hub 0
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0
uses VM inv eng 0 on hub 1
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.0
uses VM inv eng 1 on hub 1
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.1
uses VM inv eng 4 on hub 1
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec
uses VM inv eng 5 on hub 1
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: recover vram bo
from shadow start
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: recover vram bo
from shadow done
Nov 20 22:31:41 calculate kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset(2)
succeeded!
Nov 20 22:31:41 calculate kernel: [drm] Skip scheduling IBs!
Nov 20 22:31:41 calculate kernel: [drm] Skip scheduling IBs!
Nov 20 22:31:41 calculate kernel: [drm] Skip scheduling IBs!
Nov 20 22:31:41 calculate kernel: [drm] Skip scheduling IBs!
Nov 20 22:31:41 calculate kernel: [drm] Skip scheduling IBs!
--
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-20 21:58 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
2022-11-20 21:57 ` bugzilla-daemon [this message]
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-usxsIxzpfz@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).