From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68799] [APITRACE] Hyper-Z lockup with Falcon BMS 4.32u6 on CAYMAN
Date: Mon, 01 Sep 2014 17:25:05 +0000 [thread overview]
Message-ID: <bug-68799-502-4YR9sdtkQ3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68799-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 579 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68799
--- Comment #5 from smoki <smoki00790@gmail.com> ---
(In reply to comment #4)
> Setting DB_RENDER_OVERRIDE.FAST_STENCIL_DISABLE works as a workaround.
Yes it works.
But it works also with your patch set from last week, did you abandon those? I
have these 7 applied and this apitrace does not lockup :)
http://lists.freedesktop.org/archives/mesa-dev/2014-August/066388.html
http://lists.freedesktop.org/archives/mesa-dev/2014-August/066519.html
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1604 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:[~2014-09-01 17:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 23:18 [Bug 68799] New: [APITRACE] Hyper-Z lockup with Falcon BMS 4.32u6 on CAYMAN bugzilla-daemon
2013-12-02 22:54 ` [Bug 68799] " bugzilla-daemon
2013-12-31 21:13 ` bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-05-22 5:09 ` bugzilla-daemon
2014-08-05 21:12 ` bugzilla-daemon
2014-09-01 17:08 ` bugzilla-daemon
2014-09-01 17:25 ` bugzilla-daemon [this message]
2014-09-01 19:37 ` bugzilla-daemon
2014-09-09 7:37 ` bugzilla-daemon
2018-09-26 10:27 ` bugzilla-daemon
2018-09-27 11:59 ` bugzilla-daemon
2019-09-18 19:05 ` 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-68799-502-4YR9sdtkQ3@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.