From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201957] amdgpu: ring gfx timeout
Date: Sun, 28 Feb 2021 12:35:08 +0000 [thread overview]
Message-ID: <bug-201957-2300-2UzS8DeTOy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201957-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201957
Fice (fice@inbox.ru) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fice@inbox.ru
--- Comment #46 from Fice (fice@inbox.ru) ---
(In reply to MajorGonzo from comment #44)
> Here's another thing I tried which also may have made a difference. Gonna
> sound weird, but worth a try. I had a 675VA UPS that my system was plugged
> into. One time, it started shrieking (weird beepish sounds) as I was doing
> heavy gaming with lots of visual effects going on. I looked it up, and it
> seems that if your UPS, or your power strip, can't deliver enough power, it
> can cause the issues with these GPU cards. I mentioned Dec 10th as the date
> I made the change for my boot parameters, but it's also the date I plugged
> my system directly into the wall. Responding yesterday reminded me I have a
> new, more powerful UPS and I plugged my system into that today. I'll see if
> it changes anything.
>
> P.S. I know the argument...power is power...but it's not. If the surge
> protector, or UPS has cheap, thin wiring, then that restricts the amount of
> amps that can flow though them.
I had an old PSU, which was repaired once, so I replaced it. That did not
resolve the issue. The PSU is connected directly to the wall socket.
Kernel 5.10.18-200.fc33
AMD Ryzen 3 2200G with Radeon Vega Graphics
The bug is most often triggered when using Firefox.
[42174.187004] amdgpu 0000:06:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:1 pasid:32772, for process firefox pid 21156 thread
firefox:cs0 pid 21244)
[42174.187007] amdgpu 0000:06:00.0: amdgpu: in page starting at address
0x0000000000200000 from client 27
[42174.187008] amdgpu 0000:06:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00100431
[42174.187009] amdgpu 0000:06:00.0: amdgpu: Faulty UTCL2 client ID: IA
(0x2)
[42174.187010] amdgpu 0000:06:00.0: amdgpu: MORE_FAULTS: 0x1
[42174.187010] amdgpu 0000:06:00.0: amdgpu: WALKER_ERROR: 0x0
[42174.187011] amdgpu 0000:06:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[42174.187012] amdgpu 0000:06:00.0: amdgpu: MAPPING_ERROR: 0x0
[42174.187012] amdgpu 0000:06:00.0: amdgpu: RW: 0x0
... (the above messages are repeated many times)
[42184.187655] amdgpu 0000:06:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:1 pasid:32772, for process firefox pid 21156 thread
firefox:cs0 pid 21244)
[42184.187656] amdgpu 0000:06:00.0: amdgpu: in page starting at address
0x0000000000200000 from client 27
[42184.187656] amdgpu 0000:06:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00100431
[42184.187657] amdgpu 0000:06:00.0: amdgpu: Faulty UTCL2 client ID: IA
(0x2)
[42184.187657] amdgpu 0000:06:00.0: amdgpu: MORE_FAULTS: 0x1
[42184.187658] amdgpu 0000:06:00.0: amdgpu: WALKER_ERROR: 0x0
[42184.187658] amdgpu 0000:06:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[42184.187659] amdgpu 0000:06:00.0: amdgpu: MAPPING_ERROR: 0x0
[42184.187660] amdgpu 0000:06:00.0: amdgpu: RW: 0x0
[42184.328388] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=109568, emitted seq=109570
[42184.328538] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process firefox pid 21156 thread firefox:cs0 pid 21244
[42184.328542] amdgpu 0000:06:00.0: amdgpu: GPU reset begin!
[42184.330868] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd079a0 flags=0x0070]
[42184.330878] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd079c0 flags=0x0070]
[42184.330894] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd40000 flags=0x0070]
[42184.330901] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd079e0 flags=0x0070]
[42184.330909] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd40000 flags=0x0070]
[42184.330917] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd07a00 flags=0x0070]
[42184.330924] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd40000 flags=0x0070]
[42184.330942] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd07a20 flags=0x0070]
[42184.330950] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd40000 flags=0x0070]
[42184.330966] amdgpu 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x10cd07a40 flags=0x0070]
[42184.421882] [drm] free PSP TMR buffer
[42184.451954] amdgpu 0000:06:00.0: amdgpu: GPU reset succeeded, trying to
resume
[42184.452090] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).
[42184.452275] [drm] PSP is resuming...
[42184.472305] [drm] reserve 0x400000 from 0xf47fc00000 for PSP TMR
[42184.537825] amdgpu 0000:06:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[42184.546811] amdgpu 0000:06:00.0: amdgpu: RAP: optional rap ta ucode is not
available
[42184.759724] [drm] kiq ring mec 2 pipe 1 q 0
[42184.958535] amdgpu 0000:06:00.0: [drm:amdgpu_ring_test_helper [amdgpu]]
*ERROR* ring gfx test failed (-110)
[42184.958584] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of
IP block <gfx_v9_0> failed -110
[42184.958597] amdgpu 0000:06:00.0: amdgpu: GPU reset(2) failed
[42184.958667] amdgpu 0000:06:00.0: amdgpu: GPU reset end with ret = -110
[42195.061025] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[42205.292585] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[42243.148200] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=21546, emitted seq=21548
[42243.148346] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process pid 0 thread pid 0
[42243.148351] amdgpu 0000:06:00.0: amdgpu: GPU reset begin!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-02-28 12:35 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 [this message]
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
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-2UzS8DeTOy@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 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.