From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90378] [LLVM][bisected] GPU lockups in Left 4 Dead 2
Date: Sat, 23 May 2015 20:51:18 +0000 [thread overview]
Message-ID: <bug-90378-502-GDnAs0MEXG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90378-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 415 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90378
--- Comment #5 from Daniel Scharrer <daniel@constexpr.org> ---
While the glitches come from an earlier revision than the GPU lockups, both are
caused by the machine scheduler. Disabling the machine scheduler for SI fixes
both the glitches and the GPU lockups. See bug 88978 for details.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1335 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-05-23 20:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 1:24 [Bug 90378] GPU lockups in Left 4 Dead 2 bugzilla-daemon
2015-05-09 1:30 ` 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 [this message]
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-GDnAs0MEXG@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