All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31670] RV670 GPU lockup with OpenArena benchmark and kernel 2.6.37 rc1/rc2
Date: Mon, 22 Nov 2010 09:49:01 -0800 (PST)	[thread overview]
Message-ID: <20101122174902.226DF13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31670-502@http.bugs.freedesktop.org/>

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

--- Comment #8 from Alain Perrot <alain.perrot@gmail.com> 2010-11-22 09:49:02 PST ---
I have just tested with the new kernel 2.6.37-rc3 and Mesa up to commit
http://cgit.freedesktop.org/mesa/mesa/commit/?id=c63a86e1e5665fb5cd94de42d6c59171398e12ee,
which should include the one you point out.

Still the same result: GPU lockup with OpenArena benchmark and the r600g
driver.

-- 
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:[~2010-11-22 17:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 18:35 [Bug 31670] New: RV670 GPU lockup with OpenArena benchmark and kernel 2.6.37 rc1/rc2 bugzilla-daemon
2010-11-16 18:40 ` [Bug 31670] " bugzilla-daemon
2010-11-16 18:49 ` bugzilla-daemon
2010-11-21 15:27 ` bugzilla-daemon
2010-11-21 15:41 ` bugzilla-daemon
2010-11-21 16:22 ` bugzilla-daemon
2010-11-21 16:29 ` bugzilla-daemon
2010-11-22 16:32 ` bugzilla-daemon
2010-11-22 17:49 ` bugzilla-daemon [this message]
2010-11-22 18:37 ` bugzilla-daemon
2010-11-22 21:21 ` bugzilla-daemon
2010-12-07 19:12 ` bugzilla-daemon
2010-12-07 20:20 ` bugzilla-daemon
2010-12-07 22:21 ` bugzilla-daemon
2010-12-09 18:11 ` 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=20101122174902.226DF13004E@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 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.