From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94081] [radeon 3.18 regression] GPU reset recovery fails
Date: Sun, 01 Mar 2015 19:05:45 +0000 [thread overview]
Message-ID: <bug-94081-2300-3IMmNoTNNN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-94081-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=94081
--- Comment #1 from Jan Vesely <jan.vesely@rutgers.edu> ---
here's dmesg output for 3.17 kernel:
(looks like ib test on ring 5 is missing in 3.18)
[ 249.015280] radeon 0000:01:00.0: ring 0 stalled for more than 10000msec
[ 249.015287] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000742
last fence id 0x0000000000000741 on ring 0)
[ 249.027303] radeon 0000:01:00.0: ring 0 stalled for more than 10012msec
[ 249.027309] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000745
last fence id 0x0000000000000741 on ring 0)
[ 249.131987] radeon 0000:01:00.0: Saved 183 dwords of commands on ring 0.
[ 249.132005] radeon 0000:01:00.0: GPU softreset: 0x00000009
[ 249.132007] radeon 0000:01:00.0: GRBM_STATUS = 0xA0433828
[ 249.132009] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x08000007
[ 249.132010] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[ 249.132012] radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0
[ 249.132014] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[ 249.132015] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 249.132017] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00018000
[ 249.132019] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00010002
[ 249.132021] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80038647
[ 249.132023] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 249.142433] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[ 249.142486] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[ 249.143643] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828
[ 249.143644] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007
[ 249.143646] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[ 249.143648] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
[ 249.143649] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[ 249.143651] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 249.143653] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 249.143654] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[ 249.143656] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
[ 249.143658] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 249.143681] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[ 249.165960] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[ 249.167181] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
[ 249.167273] radeon 0000:01:00.0: WB enabled
[ 249.167274] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff880401eeac00
[ 249.167276] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff880401eeac0c
[ 249.168728] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc900062b2118
[ 249.185032] [drm] ring test on 0 succeeded in 3 usecs
[ 249.185042] [drm] ring test on 3 succeeded in 6 usecs
[ 249.362220] [drm] ring test on 5 succeeded in 2 usecs
[ 249.362228] [drm] UVD initialized successfully.
[ 249.362280] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
[ 249.362281] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
GFX ring (-35).
[ 249.362282] radeon 0000:01:00.0: ib ring test failed (-35).
[ 249.370592] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[ 249.377656] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[ 249.378860] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
[ 249.378951] radeon 0000:01:00.0: WB enabled
[ 249.378952] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff880401eeac00
[ 249.378954] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff880401eeac0c
[ 249.380537] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc900062b2118
[ 249.396825] [drm] ring test on 0 succeeded in 3 usecs
[ 249.396835] [drm] ring test on 3 succeeded in 7 usecs
[ 249.574006] [drm] ring test on 5 succeeded in 2 usecs
[ 249.574014] [drm] UVD initialized successfully.
[ 249.574061] [drm] ib test on ring 0 succeeded in 0 usecs
[ 249.574105] [drm] ib test on ring 3 succeeded in 0 usecs
[ 249.726529] [drm] ib test on ring 5 succeeded
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-01 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 19:02 [Bug 94081] New: [radeon 3.18 regression] GPU reset recovery fails bugzilla-daemon
2015-03-01 19:05 ` bugzilla-daemon [this message]
2015-03-02 6:58 ` [Bug 94081] " bugzilla-daemon
2015-03-04 21:10 ` bugzilla-daemon
2015-03-05 1:12 ` 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-94081-2300-3IMmNoTNNN@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).