All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201957] amdgpu: ring gfx timeout
Date: Thu, 07 Mar 2019 05:20:32 +0000	[thread overview]
Message-ID: <bug-201957-2300-Z4NYD8ru5H@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201957-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=201957

John Doe (anode.dev@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anode.dev@gmail.com

--- Comment #3 from John Doe (anode.dev@gmail.com) ---
(In reply to Alex Deucher from comment #1)
> This is more likely a mesa issue than a kernel issue.

no, 4.14 kernel with latest mesa libs works very vell without any stucks
but from 4.20.4 and in all latest kernels (including 5.0) OS freezes and stucks
every 30s ... 1min for 30s when browsing youtube with HW acceleration
enabled(uvd) or playing a game, RX550, Arch, vanilla kernel

  365.021164] amdgpu: [powerplay] 
                last message was failed ret is 0
[  365.045198] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[  365.570667] amdgpu: [powerplay] 
                failed to send message 133 ret is 0 
[  366.115228] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=9365, emitted seq=9365
[  366.115377] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process  pid 0 thread  pid 0
[  366.115388] [drm] Timeout, but no hardware hang detected.
[  366.689407] amdgpu: [powerplay] 
                last message was failed ret is 0
[  367.232287] amdgpu: [powerplay] 
                failed to send message 306 ret is 0 
[  367.787043] amdgpu: [powerplay] 
                last message was failed ret is 0
[  368.320138] amdgpu: [powerplay] 
                failed to send message 5e ret is 0 
[  369.367739] amdgpu: [powerplay] 
                last message was failed ret is 0
[  369.907559] amdgpu: [powerplay] 
                failed to send message 145 ret is 0 
[  370.994478] amdgpu: [powerplay] 
                last message was failed ret is 0
[  371.538753] amdgpu: [powerplay] 
                failed to send message 146 ret is 0 
[  372.075079] amdgpu: [powerplay] 
                last message was failed ret is 0
[  372.598565] amdgpu: [powerplay] 
                failed to send message 148 ret is 0 
[  373.657188] amdgpu: [powerplay] 
                last message was failed ret is 0
[  374.198637] amdgpu: [powerplay] 
                failed to send message 145 ret is 0 
[  375.075076] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[  375.284948] amdgpu: [powerplay] 
                last message was failed ret is 0
[  375.830347] amdgpu: [powerplay] 
                failed to send message 146 ret is 0 
[  376.138428] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=10113, emitted seq=10113
[  376.138783] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process  pid 0 thread  pid 0
[  376.138797] [drm] IP block:sdma_v3_0 is hung!
[  376.138809] [drm] GPU recovery disabled.
[  376.394657] amdgpu: [powerplay] 
                last message was failed ret is 0
[  376.934375] amdgpu: [powerplay] 
                failed to send message 16a ret is 0 
[  377.463230] amdgpu: [powerplay] 
                last message was failed ret is 0
[  377.977725] amdgpu: [powerplay] 
                failed to send message 186 ret is 0 
[  378.518406] amdgpu: [powerplay] 
                last message was failed ret is 0
[  379.060098] amdgpu: [powerplay] 
                failed to send message 54 ret is 0 
[  379.556880] amdgpu: [powerplay] 
                last message was failed ret is 0
[  380.075217] amdgpu: [powerplay] 
                failed to send message 26b ret is 0 
[  380.605976] amdgpu: [powerplay] 
                last message was failed ret is 0
[  381.134301] amdgpu: [powerplay] 
                failed to send message 13d ret is 0 
[  381.657486] amdgpu: [powerplay] 
                last message was failed ret is 0
[  382.204551] amdgpu: [powerplay] 
                failed to send message 14f ret is 0 
[  382.741827] amdgpu: [powerplay] 
                last message was failed ret is 0
[  383.281165] amdgpu: [powerplay] 
                failed to send message 151 ret is 0 
[  383.824923] amdgpu: [powerplay] 
                last message was failed ret is 0
[  384.362266] amdgpu: [powerplay] 
                failed to send message 135 ret is 0 
[  384.903686] amdgpu: [powerplay] 
                last message was failed ret is 0
[  385.101515] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[  385.461515] amdgpu: [powerplay] 
                failed to send message 190 ret is 0 
[  386.014015] amdgpu: [powerplay] 
                last message was failed ret is 0
[  386.164818] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=10761, emitted seq=10761
[  386.164970] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process  pid 0 thread  pid 0
[  386.164985] [drm] Timeout, but no hardware hang detected.

-- 
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

  parent reply	other threads:[~2019-03-07  5:20 UTC|newest]

Thread overview: 100+ 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 [this message]
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
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

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-Z4NYD8ru5H@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.