From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201957] amdgpu: ring gfx timeout
Date: Wed, 22 Jun 2022 12:56:38 +0000 [thread overview]
Message-ID: <bug-201957-2300-jhhV2qOrbk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201957-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #74 from Martin von Wittich (martin.von.wittich@iserv.eu) ---
> Did you try with the latest Linux Kernel? I had a lot of gpu lockups like this. Also try these kernel parameters : "amdgpu.ppfeaturemask=0xffffbffb amdgpu.noretry=0 amdgpu.lockup_timeout=0 amdgpu.gpu_recovery=1 amdgpu.audio=0 amdgpu.deep_color=1 amd_iommu=on iommu=pt"" ( you might also try with amdgpu.ppfeaturemask=0xfffd7fff or amdgpu.ppfeaturemask=0xffffffff )
I can confirm that at least on the current Ubuntu linux-image-oem-20.04d
kernel, these options do not resolve the issue:
```
martin@martin ~ % uname -a
Linux martin 5.14.0-1042-oem #47-Ubuntu SMP Fri Jun 3 18:17:11 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
martin@martin ~ % cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.14.0-1042-oem
root=UUID=1bd000ac-1487-4457-be1a-5ea901ded9e9 ro
amdgpu.ppfeaturemask=0xffffbffb amdgpu.noretry=0 amdgpu.lockup_timeout=0
amdgpu.gpu_recovery=1 amdgpu.audio=0 amdgpu.deep_color=1 amd_iommu=on iommu=pt
quiet
martin@martin ~ % dmesg -T | grep 'ring gfx timeout'
[Mi Jun 22 14:48:07 2022] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=1820983, emitted seq=1820985
[Mi Jun 22 14:48:18 2022] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=1820987, emitted seq=1820990
```
I had enabled these options on 2022-06-20 14:14 UTC+2, this is the first crash
I've encountered since then.
I have no idea how to build the latest kernel and therefore haven't tested that
yet.
I'll now revert back to amdgpu.dpm=0.
--
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-06-22 12:56 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 4:52 [Bug 201957] New: amdgpu: ring gfx timeout bugzilla-daemon
2018-12-11 14:57 ` [Bug 201957] " bugzilla-daemon
2018-12-11 18:18 ` bugzilla-daemon
2019-03-07 5:20 ` bugzilla-daemon
2019-03-07 5:24 ` bugzilla-daemon
2019-03-12 13:15 ` bugzilla-daemon
2019-04-01 18:20 ` bugzilla-daemon
2019-04-01 18:44 ` bugzilla-daemon
2019-08-20 15:06 ` bugzilla-daemon
2019-09-11 8:36 ` bugzilla-daemon
2019-09-20 11:37 ` bugzilla-daemon
2019-10-02 10:39 ` bugzilla-daemon
2019-10-11 22:00 ` bugzilla-daemon
2019-10-14 17:18 ` bugzilla-daemon
2019-10-24 16:39 ` bugzilla-daemon
2019-10-24 16:40 ` bugzilla-daemon
2019-10-27 18:44 ` bugzilla-daemon
2019-11-10 7:11 ` bugzilla-daemon
2019-11-25 9:43 ` bugzilla-daemon
2019-12-03 15:53 ` bugzilla-daemon
2019-12-03 16:07 ` bugzilla-daemon
2019-12-03 21:34 ` bugzilla-daemon
2019-12-04 9:54 ` bugzilla-daemon
2019-12-08 17:32 ` bugzilla-daemon
2020-01-02 8:30 ` bugzilla-daemon
2020-01-02 9:11 ` bugzilla-daemon
2020-01-19 17:03 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:13 ` bugzilla-daemon
2020-04-04 21:54 ` bugzilla-daemon
2020-05-01 9:03 ` bugzilla-daemon
2020-05-01 19:52 ` bugzilla-daemon
2020-05-25 12:21 ` bugzilla-daemon
2020-06-19 19:11 ` bugzilla-daemon
2020-08-10 23:49 ` bugzilla-daemon
2020-09-01 14:00 ` bugzilla-daemon
2020-09-13 11:14 ` bugzilla-daemon
2020-11-23 16:27 ` bugzilla-daemon
2021-01-24 19:37 ` bugzilla-daemon
2021-01-24 22:26 ` bugzilla-daemon
2021-01-24 22:51 ` bugzilla-daemon
2021-01-24 22:56 ` bugzilla-daemon
2021-01-25 22:24 ` bugzilla-daemon
2021-01-26 3:22 ` bugzilla-daemon
2021-02-14 19:48 ` bugzilla-daemon
2021-02-28 12:35 ` bugzilla-daemon
2021-03-28 13:19 ` bugzilla-daemon
2021-08-22 20:01 ` bugzilla-daemon
2021-11-17 7:14 ` bugzilla-daemon
2021-11-26 2:09 ` bugzilla-daemon
2021-12-12 21:59 ` bugzilla-daemon
2021-12-22 20:33 ` bugzilla-daemon
2022-01-01 4:29 ` bugzilla-daemon
2022-01-09 18:06 ` bugzilla-daemon
2022-01-22 23:54 ` bugzilla-daemon
2022-01-22 23:56 ` bugzilla-daemon
2022-01-24 23:17 ` bugzilla-daemon
2022-01-25 8:56 ` bugzilla-daemon
2022-01-25 18:19 ` bugzilla-daemon
2022-01-25 18:49 ` bugzilla-daemon
2022-02-02 11:39 ` bugzilla-daemon
2022-02-03 1:37 ` bugzilla-daemon
2022-02-03 1:39 ` bugzilla-daemon
2022-02-03 3:42 ` bugzilla-daemon
2022-02-11 12:23 ` bugzilla-daemon
2022-02-24 23:40 ` bugzilla-daemon
2022-02-25 14:20 ` bugzilla-daemon
2022-05-05 15:19 ` bugzilla-daemon
2022-05-05 19:14 ` bugzilla-daemon
2022-06-11 22:06 ` bugzilla-daemon
2022-06-13 1:20 ` bugzilla-daemon
2022-06-20 12:03 ` bugzilla-daemon
2022-06-20 12:06 ` bugzilla-daemon
2022-06-22 12:56 ` bugzilla-daemon [this message]
2022-06-23 10:04 ` bugzilla-daemon
2022-06-23 10:26 ` bugzilla-daemon
2022-06-23 11:05 ` bugzilla-daemon
2022-06-23 11:44 ` bugzilla-daemon
2022-06-23 22:12 ` bugzilla-daemon
2022-06-29 2:58 ` bugzilla-daemon
2022-07-14 10:17 ` bugzilla-daemon
2022-07-17 10:28 ` bugzilla-daemon
2022-07-17 20:08 ` bugzilla-daemon
2022-08-11 2:59 ` bugzilla-daemon
2023-01-11 1:13 ` bugzilla-daemon
2023-05-23 10:27 ` bugzilla-daemon
2023-05-24 8:55 ` bugzilla-daemon
2023-08-15 12:33 ` bugzilla-daemon
2023-08-24 15:52 ` bugzilla-daemon
2023-09-21 22:38 ` bugzilla-daemon
2023-09-23 1:52 ` bugzilla-daemon
2023-09-30 10:25 ` bugzilla-daemon
2023-09-30 18:57 ` bugzilla-daemon
2023-09-30 19:08 ` bugzilla-daemon
2023-09-30 19:35 ` bugzilla-daemon
2023-09-30 19:47 ` bugzilla-daemon
2023-10-21 14:29 ` bugzilla-daemon
2023-10-22 17:35 ` bugzilla-daemon
2023-10-23 17:22 ` bugzilla-daemon
2024-06-04 8:00 ` bugzilla-daemon
2024-06-04 14:27 ` bugzilla-daemon
2024-06-05 9:02 ` bugzilla-daemon
2024-06-05 9:03 ` 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-201957-2300-jhhV2qOrbk@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.