dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36812] GPU lockup in Team Fortress 2
Date: Thu,  2 Jun 2011 10:15:55 -0700 (PDT)	[thread overview]
Message-ID: <20110602171556.C94E413004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36812-502@http.bugs.freedesktop.org/>

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

--- Comment #8 from Sven Arvidsson <sa@whiz.se> 2011-06-02 10:15:55 PDT ---
(In reply to comment #7)
> With MESA_GLSL=nopt the code that was changed by the bisected commit is not
> being executed, so I think the real problem might be somewhere else.  I guess
> you could try bisecting again with MESA_GLSL=nopt and maybe you'll come up with
> a different bad commit.

I might try this. Enrico, do you remember what the good revision you used for
the bisect was, 7.10?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-06-02 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 18:36 [Bug 36812] New: GPU lockup in Team Fortress 2 bugzilla-daemon
2011-05-03 18:46 ` [Bug 36812] " bugzilla-daemon
2011-05-16 19:45 ` bugzilla-daemon
2011-05-16 19:47 ` bugzilla-daemon
2011-05-18  4:21 ` bugzilla-daemon
2011-05-19 18:16 ` bugzilla-daemon
2011-05-30 13:47 ` bugzilla-daemon
2011-05-31  9:21 ` bugzilla-daemon
2011-06-02 17:15 ` bugzilla-daemon [this message]
2011-06-03 20:54 ` bugzilla-daemon
2011-06-11 17:35 ` bugzilla-daemon
2011-06-13 22:10 ` 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=20110602171556.C94E413004F@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).