From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213145] New: AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"
Date: Wed, 19 May 2021 14:46:42 +0000 [thread overview]
Message-ID: <bug-213145-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213145
Bug ID: 213145
Summary: AMDGPU resets, timesout and crashes after "*ERROR*
Waiting for fences timed out!"
Product: Drivers
Version: 2.5
Kernel Version: 5.10.37 and 5.10.38
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: tgayoso@gmail.com
Regression: No
Created attachment 296867
--> https://bugzilla.kernel.org/attachment.cgi?id=296867&action=edit
lspci output
AMDGPU driver crashes randomly corrupting screen and freezing X with:
[ 60.449781] [drm:0xffffffffc25a7a57] *ERROR* Waiting for fences timed out!
[ 60.971941] [drm:0xffffffffc25281ae] *ERROR* ring gfx timeout, signaled
seq=3658, emitted seq=3660
[ 60.971946] [drm:0xffffffffc25281cb] *ERROR* Process information: process
Xorg pid 1192 thread Xorg:cs0 pid 1193
[ 60.971952] amdgpu 0000:05:00.0: amdgpu: GPU reset begin!
... (some output suppressed for clarity, look at attached dmesg, please).
[ 61.800343] amdgpu 0000:05:00.0: amdgpu: recover vram bo from shadow start
[ 61.800346] amdgpu 0000:05:00.0: amdgpu: recover vram bo from shadow done
[ 61.800348] [drm] Skip scheduling IBs!
[ 61.800350] [drm] Skip scheduling IBs!
[ 61.800382] [drm] Skip scheduling IBs!
[ 61.800398] amdgpu 0000:05:00.0: amdgpu: GPU reset(2) succeeded!
[ 61.800566] [drm] Skip scheduling IBs!
[ 61.800580] [drm] Skip scheduling IBs!
[ 61.800627] [drm] Skip scheduling IBs!
[ 61.801012] [drm] Skip scheduling IBs!
[ 61.801024] [drm] Skip scheduling IBs!
[ 61.801052] [drm] Skip scheduling IBs!
[ 61.801062] [drm] Skip scheduling IBs!
[ 61.801096] [drm] Skip scheduling IBs!
[ 61.801105] [drm] Skip scheduling IBs!
[ 61.801137] [drm] Skip scheduling IBs!
[ 61.801806] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.808746] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.809392] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.809764] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.810389] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.810866] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.812529] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.813359] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.814770] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 61.816488] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser
-125!
[ 62.541982] ucsi_acpi USBC000:00: PPM init failed (-110)
[ 67.004898] amdgpu_cs_ioctl: 1467 callbacks suppressed
Hardware: ASUS TUF506IU laptop (dual GPU Renoir and Nvidia GeForce GTX 1660 Ti
Mobile)
Detailed hardware in lspci.txt.
Detailed modules in lsmod.txt.
Kernle config attached in Kernel_config.
--
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:[~2021-05-19 14:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 14:46 bugzilla-daemon [this message]
2021-05-19 14:47 ` [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!" 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
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@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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