From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63748] New: GPU Lockup playing urban terror
Date: Sat, 20 Apr 2013 05:43:12 +0000 [thread overview]
Message-ID: <bug-63748-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3105 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63748
Priority: medium
Bug ID: 63748
Assignee: dri-devel@lists.freedesktop.org
Summary: GPU Lockup playing urban terror
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: dinolib@libero.it
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Playing UrT just few minutes, bring to CPU lockup rescued in some seconds with
a softreset. Sometimes the system can't recover from this state.
Before Mesa 9 (and relative dri drivers) update never happened.
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880M
[Mobility Radeon HD 4200 Series]
Kernel 3.7.6 (Chakra linux)
Environment: KDE (both OpenGL and XRender)
Tested with any kind of radeon power management (dynamic, high and low
profile).
dmesg log:
[646081.016040] radeon 0000:01:05.0: GPU lockup CP stall for more than
10000msec
[646081.016048] radeon 0000:01:05.0: GPU lockup (waiting for 0x00000000003b66b2
last fence id 0x00000000003b66ac)
[646081.017095] radeon 0000:01:05.0: Saved 185 dwords of commands on ring 0.
[646081.017099] radeon 0000:01:05.0: GPU softreset
[646081.017102] radeon 0000:01:05.0: R_008010_GRBM_STATUS=0xA00024AC
[646081.017104] radeon 0000:01:05.0: R_008014_GRBM_STATUS2=0x00000003
[646081.017106] radeon 0000:01:05.0: R_000E50_SRBM_STATUS=0x20000040
[646081.017109] radeon 0000:01:05.0: R_008674_CP_STALLED_STAT1 = 0x04000000
[646081.017111] radeon 0000:01:05.0: R_008678_CP_STALLED_STAT2 = 0x00040002
[646081.017114] radeon 0000:01:05.0: R_00867C_CP_BUSY_STAT = 0x00008484
[646081.017116] radeon 0000:01:05.0: R_008680_CP_STAT = 0x80858645
[646081.017122] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00007FEE
[646081.032099] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00000001
[646081.048074] radeon 0000:01:05.0: R_008010_GRBM_STATUS=0xA0003030
[646081.048077] radeon 0000:01:05.0: R_008014_GRBM_STATUS2=0x00000003
[646081.048079] radeon 0000:01:05.0: R_000E50_SRBM_STATUS=0x20008040
[646081.048082] radeon 0000:01:05.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[646081.048084] radeon 0000:01:05.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[646081.048086] radeon 0000:01:05.0: R_00867C_CP_BUSY_STAT = 0x00000000
[646081.048089] radeon 0000:01:05.0: R_008680_CP_STAT = 0x80100000
[646081.049090] radeon 0000:01:05.0: GPU reset succeeded, trying to resume
[646081.053294] [drm] PCIE GART of 512M enabled (table at 0x00000000C0040000).
[646081.053366] radeon 0000:01:05.0: WB enabled
[646081.053370] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr
0x00000000a0000c00 and cpu addr 0xffff8800c884dc00
[646081.053639] radeon 0000:01:05.0: setting latency timer to 64
[646081.085618] [drm] ring test on 0 succeeded in 0 usecs
[646081.094844] [drm] ib test on ring 0 succeeded in 0 usecs
No errors in Xorg.log
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4392 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-04-20 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 5:43 bugzilla-daemon [this message]
2013-04-20 19:06 ` [Bug 63748] GPU Lockup playing urban terror bugzilla-daemon
2013-04-21 19:03 ` bugzilla-daemon
2013-04-22 13:35 ` bugzilla-daemon
2013-04-22 13:39 ` bugzilla-daemon
2013-04-25 6:41 ` 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-63748-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