From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110928] wx5100 gpu crash！！！！
Date: Mon, 17 Jun 2019 06:56:34 +0000 [thread overview]
Message-ID: <bug-110928-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2498 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110928
Bug ID: 110928
Summary: wx5100 gpu crash！！！！
Product: DRI
Version: DRI git
Hardware: All
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: baopeng88_com@163.com
When we used wx5100 for rendering and encoding, we encountered some gpu hangs.
This situation is very bad and must be resolved by rebooting. The log
information is as follows. Please help analyze, thank you very much.
situation 1:
2019-06-16T14:39:24.708544+08:00|err|kernel[-]|[398383.549799] amdgpu
0005:01:00.0: GPU fault detected: 146 0x04203d0c for process a.babycard.ssvs
pid 330210 thread RenderThread pid 330511
2019-06-16T14:39:24.708703+08:00|err|kernel[-]|[398383.549803] amdgpu
0005:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00102184
2019-06-16T14:39:24.708812+08:00|err|kernel[-]|[398383.549805] amdgpu
0005:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D03D014
2019-06-16T14:39:24.708908+08:00|err|kernel[-]|[398383.549809] amdgpu
0005:01:00.0: VM fault (0x14, vmid 6, pasid 33627) at page 1057156, write from
'SDM1' (0x53444d31) (61)
After the GPU fault, about 17 seconds later:
2019-06-16T14:39:41.924400+08:00|err|kernel[-]|[398400.765123]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vce0 timeout, signaled
seq=3868950, emitted seq=3868954
2019-06-16T14:39:41.924463+08:00|info|kernel[-]|[398400.765132] [drm] GPU
recovery disabled.
situation 2：
[Thu Jun 6 22:00:14 2019] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=919191055, emitted seq=919191057
[Thu Jun 6 22:00:14 2019] [drm] GPU recovery disabled.
[Thu Jun 6 22:00:16 2019] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
sdma1 timeout, signaled seq=101603699, emitted seq=101603701
[Thu Jun 6 22:00:16 2019] [drm] GPU recovery disabled.
situation 3:
2019-06-16T14:59:05.248325+08:00|err|kernel[-]|[399194.411704]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled
seq=230984670, emitted seq=230984673
2019-06-16T14:59:05.248404+08:00|info|kernel[-]|[399194.411708] [drm] GPU
recovery disabled.
can you help me to analyze these situations to solve these problems? thank you.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3774 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-06-17 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 6:56 bugzilla-daemon [this message]
2019-06-17 6:58 ` [Bug 110928] wx5100 gpu crash！！！！ bugzilla-daemon
2019-06-17 7:01 ` bugzilla-daemon
2019-06-17 10:15 ` [Bug 110928] wx5100 gpu crash bugzilla-daemon
2019-11-19 9:31 ` 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-110928-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.