From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90378] GPU lockups in Left 4 Dead 2
Date: Sat, 09 May 2015 01:24:59 +0000 [thread overview]
Message-ID: <bug-90378-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1642 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90378
Bug ID: 90378
Summary: GPU lockups in Left 4 Dead 2
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: daniel@constexpr.org
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 115653
--> https://bugs.freedesktop.org/attachment.cgi?id=115653&action=edit
dmesg output
While playing L4D2 today I got a lot of GPU lockups.
While the lockups seem to happen randomly, they are fairly easy to reproduce in
the third chapter (The Mall) of the Dead Center campaign. I recorded an
apitrace while encountering 3 lockups and there seem to be at least a couple of
lockups each time I retrace it:
http://constexpr.org/tmp/L4D2-radeonsi.trace.xz (507 MiB)
At least driver was able to successfully reset the GPU each time.
There also seem to be some infrequent rendering glitches.
Probably related to bug 89228, and possibly bug 90217, bug 90284 and/or bug
89954 (all reports of lockups with Source engine games).
GPU; Radeon HD 7950 (TAHITI)
Mesa 10.6.0-devel (git-3bdbc1e)
LLVM r236436
Linux 4.0.1-gentoo
The above logs and apitrace were recorded with unsafe-fp-math enbled (see bug
89069 comment 34) but the lockups also happen without it. I also noticed some
VM fault messages in dmesg while running L4D2 without unsafe-fp-math.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3893 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:[~2015-05-09 1:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 1:24 bugzilla-daemon [this message]
2015-05-09 1:30 ` [Bug 90378] GPU lockups in Left 4 Dead 2 bugzilla-daemon
2015-05-09 1:30 ` bugzilla-daemon
2015-05-21 15:09 ` bugzilla-daemon
2015-05-21 15:09 ` [Bug 90378] [radeonsi][bisected] " bugzilla-daemon
2015-05-21 15:13 ` bugzilla-daemon
2015-05-21 15:14 ` bugzilla-daemon
2015-05-21 15:16 ` bugzilla-daemon
2015-05-22 2:32 ` [Bug 90378] [LLVM][bisected] " bugzilla-daemon
2015-05-23 20:51 ` bugzilla-daemon
2015-07-03 15:27 ` bugzilla-daemon
2015-07-03 19:03 ` bugzilla-daemon
2015-07-05 1:11 ` bugzilla-daemon
2015-07-29 7:18 ` bugzilla-daemon
2015-08-01 14:20 ` 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-90378-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.