From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35095] [r300g] HiZ broken in WoW
Date: Sat, 25 Jun 2011 07:18:01 -0700 (PDT) [thread overview]
Message-ID: <20110625141801.E7EE913004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-35095-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=35095
--- Comment #12 from Chris Rankin <rankincj@googlemail.com> 2011-06-25 07:18:01 PDT ---
(In reply to comment #11)
> I've just retested WoW with HiZ enabled on my M66GL and the 2.6.39.1 kernel,
> and my dmesg log now fills up with these messages:
>
> [drm:r100_cs_track_check] *ERROR* [drm] No buffer for z buffer !
> [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
This is no longer happening with 2.6.39.2 kernel and latest Mesa from git.
Original corruption has been restored.
--
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:[~2011-06-25 14:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 22:09 [Bug 35095] New: [r300g] More screen corruption in WoW with HyperZ enabled bugzilla-daemon
2011-03-07 22:14 ` [Bug 35095] " bugzilla-daemon
2011-03-07 22:19 ` bugzilla-daemon
2011-03-07 22:23 ` bugzilla-daemon
2011-03-08 21:15 ` bugzilla-daemon
2011-03-08 21:21 ` bugzilla-daemon
2011-03-08 21:25 ` bugzilla-daemon
2011-03-08 22:25 ` bugzilla-daemon
2011-03-08 23:13 ` bugzilla-daemon
2011-03-08 23:17 ` [Bug 35095] [r300g] HiZ broken in WoW bugzilla-daemon
2011-03-08 23:24 ` bugzilla-daemon
2011-05-15 1:40 ` bugzilla-daemon
2011-05-15 12:06 ` bugzilla-daemon
2011-06-23 7:55 ` bugzilla-daemon
2011-06-25 14:18 ` bugzilla-daemon [this message]
2012-12-02 6:13 ` bugzilla-daemon
2012-12-02 12:38 ` bugzilla-daemon
2012-12-02 21:49 ` bugzilla-daemon
2012-12-02 22:00 ` 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=20110625141801.E7EE913004F@annarchy.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;
as well as URLs for NNTP newsgroup(s).