From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 45290] [bisected r200] fdo23670-drawpix_stencil fails and crashes
Date: Wed, 01 Feb 2012 06:25:22 +0000 [thread overview]
Message-ID: <bug-45290-502-ffsBuMujyo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-45290-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=45290
--- Comment #4 from Ian Romanick <idr@freedesktop.org> 2012-01-31 22:25:22 PST ---
(In reply to comment #2)
> Can you upgrade to a DDX from -git?
>
> I think the fix is in there, it was allocating too small depth buffers.
I can, but it won't be until next week. I'm currently traveling.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-02-01 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 1:37 [Bug 45290] New: [bisected r200] fdo23670-drawpix_stencil fails and crashes bugzilla-daemon
2012-01-27 2:02 ` [Bug 45290] " bugzilla-daemon
2012-01-28 12:14 ` bugzilla-daemon
2012-01-28 12:15 ` bugzilla-daemon
2012-02-01 6:25 ` bugzilla-daemon [this message]
2014-01-22 1:54 ` 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-45290-502-ffsBuMujyo@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