From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103634] nv_conditional_render tests hang the gpu (HD 5750)
Date: Thu, 09 Nov 2017 02:53:38 +0000 [thread overview]
Message-ID: <bug-103634-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3250 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103634
Bug ID: 103634
Summary: nv_conditional_render tests hang the gpu (HD 5750)
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: sroland@vmware.com
QA Contact: dri-devel@lists.freedesktop.org
Nearly all of piglit's nv_conditional_render tests (I think 10 out of 12, I'd
rather not retry them all since it sometimes brings down the box after the gpu
reset) immediately hang the gpu - nv_conditional_render-begin-xxx are the two
exceptions (which pass).
GPU is Juniper, HD 5750.
I'm not sure if this is even a regression, as I never ran piglit on this box
before, and at least with mesa 17.1.8 it hangs all the same as current git
master. If the kernel version matters, I tried some 4.9 and some 4.13 kernel.
[ 749.782315] radeon 0000:01:00.0: ring 0 stalled for more than 10224msec
[ 749.782319] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000004081 last fence id 0x0000000000004
...
[ 771.466593] radeon 0000:01:00.0: Saved 882 dwords of commands on ring 0.
[ 771.906456] radeon 0000:01:00.0: GPU softreset: 0x0000001D
[ 771.906458] radeon 0000:01:00.0: GRBM_STATUS = 0xA0001828
[ 771.906459] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000003
[ 771.906460] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[ 771.906461] radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0
[ 771.906462] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[ 771.906463] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 771.906464] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 771.906465] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000006
[ 771.906466] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80008E47
[ 771.906468] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 771.914331] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[ 771.914382] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100
[ 771.915528] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828
[ 771.915529] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007
[ 771.915530] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[ 771.915531] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
[ 771.915532] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[ 771.915533] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 771.915534] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 771.915535] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[ 771.915536] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
[ 771.915538] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 771.915554] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4625 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-11-09 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 2:53 bugzilla-daemon [this message]
2017-11-09 4:42 ` [Bug 103634] nv_conditional_render tests hang the gpu (HD 5750) bugzilla-daemon
2019-09-18 19:24 ` 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-103634-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.