From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91268] R6xx freezes with kernel 3.17 and up
Date: Fri, 24 Jul 2015 19:38:21 +0000 [thread overview]
Message-ID: <bug-91268-502-3mrhAoPSPp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91268-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3725 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91268
Fedja Beader <fedja.beader@t-2.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fedja.beader@t-2.net
--- Comment #20 from Fedja Beader <fedja.beader@t-2.net> ---
This patch seems (for 1h now) to work on 4.0.8 + Gentoo + grsecurity
For me, the screen froze with the graphics still visible. Additionally, the
game was still running in the background (heard sounds and spewed errors in
console) and I had full ssh access. In another game the screen turned black and
white +something that looked like missing textures, but I could still interact
with it.
Happened on both 3.18.9 + Gentoo + grsecurity and above mentioned 4.0.8
mesa is at 10.3
lspci:
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82
[Mobility Radeon HD 3450/3470]
[ 3936.443037] radeon 0000:01:00.0: ring 0 stalled for more than 10273msec
[ 3936.443046] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000050ded last fence id 0x0000000000050df3 on ring 0)
[ 3936.450174] radeon 0000:01:00.0: Saved 185 dwords of commands on ring 0.
[ 3936.450191] radeon 0000:01:00.0: GPU softreset: 0x00000008
[ 3936.450197] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0xA0003030
[ 3936.450202] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000003
[ 3936.450207] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200000C0
[ 3936.450212] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 3936.450216] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 3936.450221] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00020186
[ 3936.450226] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80028645
[ 3936.450231] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 3936.501715] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00004001
[ 3936.501773] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[ 3936.503883] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0xA0003030
[ 3936.503888] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000003
[ 3936.503893] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200080C0
[ 3936.503898] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 3936.503903] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 3936.503907] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[ 3936.503912] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80100000
[ 3936.503917] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 3936.503929] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[ 3936.523106] [drm] PCIE GART of 512M enabled (table at 0x0000000000254000).
[ 3936.523152] radeon 0000:01:00.0: WB enabled
[ 3936.523160] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000010000c00 and cpu addr 0xffff880074d72c00
[ 3936.524373] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x00000000000521d0 and cpu addr 0xffffc900045921d0
[ 3936.556287] [drm] ring test on 0 succeeded in 0 usecs
[ 3936.732365] [drm] ring test on 5 succeeded in 1 usecs
[ 3936.732375] [drm] UVD initialized successfully.
[ 3946.943038] radeon 0000:01:00.0: ring 0 stalled for more than 10213msec
[ 3946.943047] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000050dee last fence id 0x0000000000050df3 on ring 0)
[ 3946.956388] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
[ 3946.956396] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
GFX ring (-35).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4987 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 prev parent reply other threads:[~2015-07-24 19:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:15 [Bug 91268] R6xx freezes with kernel 3.17 and up bugzilla-daemon
2015-07-11 19:20 ` bugzilla-daemon
2015-07-12 2:20 ` bugzilla-daemon
2015-07-12 12:37 ` bugzilla-daemon
2015-07-13 14:19 ` bugzilla-daemon
2015-07-13 15:30 ` bugzilla-daemon
2015-07-15 3:30 ` bugzilla-daemon
2015-07-15 12:27 ` bugzilla-daemon
2015-07-15 12:29 ` bugzilla-daemon
2015-07-16 3:52 ` bugzilla-daemon
2015-07-16 13:12 ` bugzilla-daemon
2015-07-16 13:56 ` bugzilla-daemon
2015-07-16 13:58 ` bugzilla-daemon
2015-07-16 14:37 ` bugzilla-daemon
2015-07-16 14:43 ` bugzilla-daemon
2015-07-16 14:49 ` bugzilla-daemon
2015-07-16 15:03 ` bugzilla-daemon
2015-07-16 16:15 ` bugzilla-daemon
2015-07-17 3:06 ` bugzilla-daemon
2015-07-17 3:30 ` bugzilla-daemon
2015-07-24 19:38 ` bugzilla-daemon [this message]
2015-07-24 19:42 ` bugzilla-daemon
2015-08-04 10:00 ` bugzilla-daemon
2015-08-04 14:33 ` bugzilla-daemon
2015-10-29 20:34 ` bugzilla-daemon
2015-11-26 8:17 ` bugzilla-daemon
2016-01-29 2:42 ` bugzilla-daemon
2016-03-22 15:54 ` 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-91268-502-3mrhAoPSPp@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