From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69328] New: Recoverable and unrecoverable lockups with opencl-example on trinity APU
Date: Fri, 13 Sep 2013 17:10:25 +0000 [thread overview]
Message-ID: <bug-69328-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 5731 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69328
Priority: medium
Bug ID: 69328
Assignee: dri-devel@lists.freedesktop.org
Summary: Recoverable and unrecoverable lockups with
opencl-example on trinity APU
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: slicksam@gmx.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
Software in use:
Up to date mesa, llvm, clang, libclc, firmware, as of 20130910. Gentoo's Linux
3.11. opencl-example-12905ac620b83713b07ece763ff3c36fb3c2e7e5.
Hardware in use: AMD A8 5600K APU (Radeon HD 7560D, Aruba), 32GB system RAM,
Biostar Hi-Fi A85W motherboard.
Steps to reproduce:
Run hello_world program from opencl-example. First run works correctly.
Second run either completely locks up the machine or locks up the GPU (which
recovers after a short time). Same behavior for other tests - the first test
completes and the second causes problems.
This is what the second opencl-example run looks like:
localhost opencl-example-12905ac620b83713b07ece763ff3c36fb3c2e7e5 #
./hello_world
There are 1 platforms.
There are 1 GPU devices.
clCreateContext() succeeded.
clCreateCommandQueue() succeeded.
clCreateProgramWithSource() suceeded.
clBuildProgram() suceeded.
clCreateKernel() suceeded.
clCreateBuffer() succeeded.
clSetKernelArg() succeeded.
clEnqueueNDRangeKernel() suceeded.
((( 10 second hang here, or forever if the machine is toast )))
clEnqueueReadBuffer() suceeded.
pi = 3.141590
And, here is the dmesg output from the recoverable lockups:
[ 1365.806285] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec
[ 1365.806292] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000007ec3
last fence id 0x0000000000007ec2)
[ 1365.821261] radeon 0000:00:01.0: Saved 559 dwords of commands on ring 0.
[ 1365.821293] radeon 0000:00:01.0: GPU softreset: 0x00000008
[ 1365.821297] radeon 0000:00:01.0: GRBM_STATUS = 0xB0003828
[ 1365.821300] radeon 0000:00:01.0: GRBM_STATUS_SE0 = 0x00000007
[ 1365.821304] radeon 0000:00:01.0: GRBM_STATUS_SE1 = 0x00000007
[ 1365.821307] radeon 0000:00:01.0: SRBM_STATUS = 0x20000040
[ 1365.821332] radeon 0000:00:01.0: SRBM_STATUS2 = 0x00000000
[ 1365.821335] radeon 0000:00:01.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 1365.821338] radeon 0000:00:01.0: R_008678_CP_STALLED_STAT2 = 0x40000000
[ 1365.821341] radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT = 0x00010002
[ 1365.821344] radeon 0000:00:01.0: R_008680_CP_STAT = 0x80220243
[ 1365.821347] radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 1365.821350] radeon 0000:00:01.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
[ 1365.821354] radeon 0000:00:01.0: VM_CONTEXT0_PROTECTION_FAULT_ADDR
0x00000000
[ 1365.821357] radeon 0000:00:01.0: VM_CONTEXT0_PROTECTION_FAULT_STATUS
0x00000000
[ 1365.821360] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 1365.821363] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 1365.827029] radeon 0000:00:01.0: GRBM_SOFT_RESET=0x00004001
[ 1365.827083] radeon 0000:00:01.0: SRBM_SOFT_RESET=0x00000100
[ 1365.828237] radeon 0000:00:01.0: GRBM_STATUS = 0x00003828
[ 1365.828240] radeon 0000:00:01.0: GRBM_STATUS_SE0 = 0x00000007
[ 1365.828243] radeon 0000:00:01.0: GRBM_STATUS_SE1 = 0x00000007
[ 1365.828246] radeon 0000:00:01.0: SRBM_STATUS = 0x20000040
[ 1365.828271] radeon 0000:00:01.0: SRBM_STATUS2 = 0x00000000
[ 1365.828274] radeon 0000:00:01.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 1365.828277] radeon 0000:00:01.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 1365.828280] radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT = 0x00000000
[ 1365.828283] radeon 0000:00:01.0: R_008680_CP_STAT = 0x00000000
[ 1365.828286] radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 1365.828289] radeon 0000:00:01.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
[ 1365.828317] radeon 0000:00:01.0: GPU reset succeeded, trying to resume
[ 1365.843638] [drm] PCIE GART of 512M enabled (table at 0x0000000000276000).
[ 1365.843775] radeon 0000:00:01.0: WB enabled
[ 1365.843781] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000020000c00 and cpu addr 0xffff8807dea6bc00
[ 1365.844520] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffc900057b5a18
[ 1365.844524] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr
0x0000000020000c04 and cpu addr 0xffff8807dea6bc04
[ 1365.844528] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr
0x0000000020000c08 and cpu addr 0xffff8807dea6bc08
[ 1365.844532] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr
0x0000000020000c0c and cpu addr 0xffff8807dea6bc0c
[ 1365.844536] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr
0x0000000020000c10 and cpu addr 0xffff8807dea6bc10
[ 1365.863416] [drm] ring test on 0 succeeded in 2 usecs
[ 1365.863477] [drm] ring test on 3 succeeded in 2 usecs
[ 1365.863485] [drm] ring test on 4 succeeded in 1 usecs
[ 1365.909450] [drm] ring test on 5 succeeded in 1 usecs
[ 1365.909454] [drm] UVD initialized successfully.
[ 1365.936524] [drm] ib test on ring 0 succeeded in 0 usecs
[ 1365.937056] [drm] ib test on ring 3 succeeded in 0 usecs
[ 1365.937581] [drm] ib test on ring 4 succeeded in 0 usecs
[ 1365.958519] [drm] ib test on ring 5 succeeded
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 7039 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-09-13 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 17:10 bugzilla-daemon [this message]
2013-09-13 17:17 ` [Bug 69328] Recoverable and unrecoverable lockups with opencl-example on trinity APU bugzilla-daemon
2013-09-13 23:29 ` bugzilla-daemon
2013-09-15 6:09 ` bugzilla-daemon
2013-09-15 10:14 ` bugzilla-daemon
2013-09-15 18:00 ` bugzilla-daemon
2013-09-15 22:50 ` bugzilla-daemon
2013-09-17 13:39 ` bugzilla-daemon
2013-09-17 16:04 ` bugzilla-daemon
2013-09-17 16:09 ` bugzilla-daemon
2013-09-17 16:16 ` bugzilla-daemon
2013-09-17 16:43 ` bugzilla-daemon
2013-09-17 16:50 ` 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-69328-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 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).