From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42683] [r300g] GPU lockup while playing WoW
Date: Mon, 07 Nov 2011 23:13:25 +0000 [thread overview]
Message-ID: <bug-42683-502-zyGEFfJFvg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42683-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=42683
--- Comment #2 from Chris Rankin <rankincj@googlemail.com> 2011-11-07 15:13:25 PST ---
(In reply to comment #1)
> Could you please bisect?
Haven't we already played the bisection game, though? I proved that commit:
363ff844753c46ac9c13866627e096b091ea81f8 is the first bad commit
commit 363ff844753c46ac9c13866627e096b091ea81f8
Author: Marek Olšák <maraeo@gmail.com>
Date: Tue Sep 27 01:10:20 2011 +0200
winsys/radeon: move GEM domains out of the drivers into winsys
was bad ages ago, and have already mentioned getting a GPU lockup with it
applied. Any new bisection must therefore include this "known bad" commit.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-11-07 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 21:31 [Bug 42683] New: [r300g] GPU lockup while playing WoW bugzilla-daemon
2011-11-07 16:44 ` [Bug 42683] " bugzilla-daemon
2011-11-07 22:50 ` bugzilla-daemon
2011-11-07 23:13 ` bugzilla-daemon [this message]
2011-11-22 20:57 ` bugzilla-daemon
2012-06-08 13:44 ` 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-42683-502-zyGEFfJFvg@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