dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89228] Regression with left for dead 2
Date: Thu, 19 Feb 2015 19:54:17 +0000	[thread overview]
Message-ID: <bug-89228-502-qyojh9X5P8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89228-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 638 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=89228

--- Comment #2 from Daniel Scharrer <daniel@constexpr.org> ---
Did you try the patch form 88561 comment 6. I still see some glitches in your
trace with that patch, although it may be worse without it (didn't test).
Didn't get any GPU lockups or errors in dmesg with the trace, even after
running it a couple of times.

GPU: Radeon HD 7950 (OpenGL renderer string: Gallium 0.4 on AMD TAHITI)
Mesa git-6c34fd2 + "radeonsi: don't use SQC_CACHES to flush ICACHE and KCACHE
on SI"
LLVM r229671
Kernel 3.19.0-gentoo

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1420 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

  parent reply	other threads:[~2015-02-19 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 14:12 [Bug 89228] Regression with left for dead 2 bugzilla-daemon
2015-02-19 17:22 ` bugzilla-daemon
2015-02-19 19:54 ` bugzilla-daemon [this message]
2015-02-20  3:25 ` bugzilla-daemon
2015-02-21 15:00 ` bugzilla-daemon
2015-05-09  1:30 ` bugzilla-daemon
2015-05-21 15:21 ` bugzilla-daemon
2015-07-03 15:40 ` bugzilla-daemon
2015-08-14 21:52 ` 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-89228-502-qyojh9X5P8@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