From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66352] New: GPU lockup in L4D2 on TURKS with HyperZ
Date: Sat, 29 Jun 2013 03:42:33 +0000 [thread overview]
Message-ID: <bug-66352-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4665 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66352
Priority: medium
Bug ID: 66352
Assignee: dri-devel@lists.freedesktop.org
Summary: GPU lockup in L4D2 on TURKS with HyperZ
Severity: normal
Classification: Unclassified
OS: FreeBSD
Reporter: russianneuromancer@ya.ru
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 81668
--> https://bugs.freedesktop.org/attachment.cgi?id=81668&action=edit
dmesg
Lockup described in bug 64220 was happen right after campaign start (in first
minute) but this lockup usually happen later - in first hour of playing. This
lockup is not reproducible when HyperZ is disabled, so probably (like bug
64220) is related to HyperZ.
[ 2160.750951] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 2160.750966] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000002525f
last fence id 0x000000000002525c)
[ 2160.786068] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000174118 and cpu addr 0xffffc9000681c118
[ 2160.787147] radeon 0000:01:00.0: Saved 183 dwords of commands on ring 0.
[ 2160.787166] radeon 0000:01:00.0: GPU softreset: 0x00000019
[ 2160.787175] radeon 0000:01:00.0: GRBM_STATUS = 0xE7730CA0
[ 2160.787177] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000001
[ 2160.787180] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[ 2160.787182] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
[ 2160.787184] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[ 2160.787186] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000
[ 2160.787189] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x000D1000
[ 2160.787191] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00068506
[ 2160.787193] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80878647
[ 2160.787196] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 2160.787356] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[ 2160.787410] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[ 2160.788559] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828
[ 2160.788561] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007
[ 2160.788563] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[ 2160.788565] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
[ 2160.788568] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[ 2160.788570] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 2160.788572] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 2160.788574] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[ 2160.788576] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
[ 2160.788579] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 2160.788589] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[ 2160.793777] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 2160.793895] radeon 0000:01:00.0: WB enabled
[ 2160.793900] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff8801fb519c00
[ 2160.793904] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff8801fb519c0c
[ 2160.796145] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000174118 and cpu addr 0xffffc900079b2118
[ 2160.812389] [drm] ring test on 0 succeeded in 2 usecs
[ 2160.812457] [drm] ring test on 3 succeeded in 1 usecs
[ 2160.987496] [drm] ring test on 5 succeeded in 1 usecs
[ 2160.987512] [drm] UVD initialized successfully.
[ 2161.219416] [drm] ib test on ring 0 succeeded in 0 usecs
[ 2161.219497] [drm] ib test on ring 3 succeeded in 1 usecs
[ 2161.370073] [drm:r600_uvd_ib_test] *ERROR* radeon: failed to get create msg
(-22).
[ 2161.370094] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-22).
~$ lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
BeaverCreek [Radeon HD 6620G]
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
Whistler [Radeon HD 6600M/6700M/7600M Series]
(DRI_PRIME is used to launch game.)
Linux 3.10-rc7
libdrm 2.4.45+git20130607.a0178c00
Mesa 9.2.0~git20130627.15085b47
xserver-xorg-video-radeon 7.1.99+git20130531.bd2557ea
Xserver 1.13.4~git20130508+server-1.13-branch.10c42f57
Kubuntu 13.04 x86_64 updated from Xorg Edgers PPA.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6399 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-06-29 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 3:42 bugzilla-daemon [this message]
2014-01-23 13:53 ` [Bug 66352] GPU lockup in L4D2 on TURKS with HyperZ bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-08-24 13:47 ` bugzilla-daemon
2016-02-19 10:58 ` 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-66352-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).