From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199749] amdgpu on Ryzen 2400G freeze randomly
Date: Sat, 30 Jun 2018 04:17:36 +0000 [thread overview]
Message-ID: <bug-199749-2300-L1lzqf9Kj2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199749-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199749
--- Comment #29 from notsyncing (song.fc@gmail.com) ---
I just upgraded to mesa 18.1.3 and kernel 4.17.3. I ran firefox with
GALLIUM_DDEBUG after reboot. It produces these after I opened some tabs and
firefox stopped responsing.
---
Gallium debugger active. Logging all calls.
Hang detection timeout is 1000ms.
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000000
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000001
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000002
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000003
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000004
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000005
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000006
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000007
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000008
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000009
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000010
dd: can't create a directory (13)
dd: can't create a directory (13)
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000011
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000012
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000013
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000014
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000015
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000016
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000017
dd: can't create a directory (13)
dd: failed to open /home/sfc/ddebug_dumps/firefox_5057_00000018
GPU hang detected, collecting information...
Draw # driver prev BOP TOP BOP dump file
-------------------------------------------------------------
8 YES NO NO NO dd: can't create a directory (13)
fopen failed
Done.
Sandbox: seccomp sandbox violation: pid 5057, tid 5268, syscall 162, args
140631883336544 7 140633020008624 140632174061559 7 140632344285188.
dd: Aborting the process...
[Parent 4748, Gecko_IOThread] WARNING: pipe error (72): 连接被对方重设: file
/build/firefox-m9FtQy/firefox-60.0.2+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 353
[Parent 4748, Gecko_IOThread] WARNING: pipe error (113): 连接被对方重设: file
/build/firefox-m9FtQy/firefox-60.0.2+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 353
###!!! [Parent][MessageChannel] Error:
(msgtype=0x15007F,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
---
The umr commands are:
---
sfc@sfc-DESKTOP:~$ sudo umr -lb
raven1.gfx91
raven1.vcn10
raven1.dcn10
raven1.nbio70
raven1.sdma041
raven1.hdp40
raven1.oss40
raven1.mmhub91
raven1.mp100
sfc@sfc-DESKTOP:~$ sudo umr -O verbose,follow_ib -R gfx[.]
error: Unknown option [follow_ib]
sfc@sfc-DESKTOP:~$ sudo umr -O bits -wa
No active waves!
sfc@sfc-DESKTOP:~$ sudo umr -O many,bits -r*.*.mmGRBM_STATUS
[ERROR]: Unknown option <-r*.*.mmGRBM_STATUS>
sfc@sfc-DESKTOP:~$ sudo umr -O many,bits -r *.*.HEADER_DUMP
gfx91.mmCP_MEC_ME1_HEADER_DUMP => 0xc0000e00
.HEADER_DUMP[0:31] ==
3221229056 (0xc0000e00)
gfx91.mmCP_MEC_ME2_HEADER_DUMP => 0xdef0def0
.HEADER_DUMP[0:31] ==
3740327664 (0xdef0def0)
gfx91.mmCP_ME_HEADER_DUMP => 0xc0004200
.ME_HEADER_DUMP[0:31] ==
3221242368 (0xc0004200)
gfx91.mmCP_PFP_HEADER_DUMP => 0xffff1000
.PFP_HEADER_DUMP[0:31] ==
4294905856 (0xffff1000)
gfx91.mmCP_CE_HEADER_DUMP => 0xffff1000
.CE_HEADER_DUMP[0:31] ==
4294905856 (0xffff1000)
sfc@sfc-DESKTOP:~$ sudo umr -O many,bits -r *.*.CP_EOP
gfx91.mmCP_EOPQ_WAIT_TIME => 0x0000052c
.WAIT_TIME[0:9] ==
300 (0x0000012c)
.SCALE_COUNT[10:17] ==
1 (0x00000001)
gfx91.mmCP_EOP_DONE_ADDR_LO => 0x00609000
.ADDR_LO[2:31] ==
1582080 (0x00182400)
gfx91.mmCP_EOP_DONE_ADDR_HI => 0x000000f5
.ADDR_HI[0:15] ==
245 (0x000000f5)
gfx91.mmCP_EOP_DONE_DATA_LO => 0x00001d01
.DATA_LO[0:31] ==
7425 (0x00001d01)
gfx91.mmCP_EOP_DONE_DATA_HI => 0x00000000
.DATA_HI[0:31] ==
0 (0x00000000)
gfx91.mmCP_EOP_LAST_FENCE_LO => 0x00001d01
.LAST_FENCE_LO[0:31] ==
7425 (0x00001d01)
gfx91.mmCP_EOP_LAST_FENCE_HI => 0x00000000
.LAST_FENCE_HI[0:31] ==
0 (0x00000000)
gfx91.mmCP_EOP_DONE_EVENT_CNTL => 0x00038060
.WBINV_TC_OP[0:6] ==
96 (0x00000060)
.WBINV_ACTION_ENA[12:17] ==
56 (0x00000038)
.CACHE_POLICY[25:25] ==
0 (0x00000000)
.EXECUTE[28:28] ==
0 (0x00000000)
gfx91.mmCP_EOP_DONE_DATA_CNTL => 0x40010000
.DST_SEL[16:17] ==
1 (0x00000001)
.INT_SEL[24:26] ==
0 (0x00000000)
.DATA_SEL[29:31] ==
2 (0x00000002)
gfx91.mmCP_EOP_DONE_CNTX_ID => 0x00000000
.CNTX_ID[0:31] ==
0 (0x00000000)
---
No GPU hang log in dmesg.
--
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:[~2018-06-30 4:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 9:21 [Bug 199749] New: amdgpu on Ryzen 2400G freeze randomly bugzilla-daemon
2018-06-12 21:27 ` [Bug 199749] " bugzilla-daemon
2018-06-13 7:17 ` bugzilla-daemon
2018-06-16 15:47 ` bugzilla-daemon
2018-06-16 16:29 ` bugzilla-daemon
2018-06-16 18:24 ` bugzilla-daemon
2018-06-16 18:31 ` bugzilla-daemon
2018-06-16 18:59 ` bugzilla-daemon
2018-06-17 9:37 ` bugzilla-daemon
2018-06-17 9:41 ` bugzilla-daemon
2018-06-18 6:16 ` bugzilla-daemon
2018-06-18 8:55 ` bugzilla-daemon
2018-06-21 13:34 ` bugzilla-daemon
2018-06-21 16:23 ` bugzilla-daemon
2018-06-24 6:12 ` bugzilla-daemon
2018-06-25 14:30 ` bugzilla-daemon
2018-06-26 12:03 ` bugzilla-daemon
2018-06-26 12:04 ` bugzilla-daemon
2018-06-26 12:40 ` bugzilla-daemon
2018-06-26 12:40 ` bugzilla-daemon
2018-06-26 14:58 ` bugzilla-daemon
2018-06-26 16:55 ` bugzilla-daemon
2018-06-27 11:44 ` bugzilla-daemon
2018-06-27 13:39 ` bugzilla-daemon
2018-06-29 19:59 ` bugzilla-daemon
2018-06-29 20:03 ` bugzilla-daemon
2018-06-30 3:09 ` bugzilla-daemon
2018-06-30 3:10 ` bugzilla-daemon
2018-06-30 4:17 ` bugzilla-daemon [this message]
2018-07-01 6:57 ` bugzilla-daemon
2018-07-01 8:56 ` bugzilla-daemon
2018-07-01 9:00 ` bugzilla-daemon
2018-07-14 6:45 ` bugzilla-daemon
2018-08-02 20:02 ` bugzilla-daemon
2018-08-04 4:46 ` 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-199749-2300-L1lzqf9Kj2@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;
as well as URLs for NNTP newsgroup(s).