All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29556] [rv620] GPU reset followed by black screen
Date: Sun,  5 Sep 2010 15:45:22 -0700 (PDT)	[thread overview]
Message-ID: <20100905224522.BC30D1300AC@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29556-502@http.bugs.freedesktop.org/>

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

--- Comment #19 from Andy Furniss <lists@andyfurniss.entadsl.com> 2010-09-05 15:45:22 PDT ---
(In reply to comment #18)
> seems the bug I was seeing (see comment #5) is fixed by v3 fencing patch, so
> for me it is ready to be closed...

I have failed to reproduce the one lockup I had with various d-r-ts, and now am
running d-r-t + v3 fence.

-- 
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-09-05 22:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 11:01 [Bug 29556] New: [rv620] GPU reset followed by black screen bugzilla-daemon
2010-08-13 11:03 ` [Bug 29556] " bugzilla-daemon
2010-08-13 12:14 ` bugzilla-daemon
2010-08-15 11:45 ` bugzilla-daemon
2010-08-15 14:02 ` bugzilla-daemon
2010-08-16 17:40 ` bugzilla-daemon
2010-08-16 17:43 ` bugzilla-daemon
2010-08-16 18:02 ` bugzilla-daemon
2010-08-16 21:13 ` bugzilla-daemon
2010-08-16 21:44 ` bugzilla-daemon
2010-08-17  8:39 ` bugzilla-daemon
2010-08-17 14:44 ` bugzilla-daemon
2010-08-17 19:12 ` bugzilla-daemon
2010-08-17 19:14 ` bugzilla-daemon
2010-08-17 19:38 ` bugzilla-daemon
2010-08-17 21:05 ` bugzilla-daemon
2010-08-17 21:09 ` bugzilla-daemon
2010-08-18 10:20 ` bugzilla-daemon
2010-09-01 13:59 ` bugzilla-daemon
2010-09-05 17:30 ` bugzilla-daemon
2010-09-05 22:45 ` bugzilla-daemon [this message]
2010-09-07  6:14 ` 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=20100905224522.BC30D1300AC@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.