dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79051] Panic with radeon hd 5750, bisected
Date: Sat, 28 Jun 2014 14:02:22 +0000	[thread overview]
Message-ID: <bug-79051-2300-7SF7vYG6n1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-79051-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=79051

--- Comment #2 from Ed Tomlinson <edt@aei.ca> ---
I am seeing a similar panic on a R7 260X.

See:
https://plus.google.com/u/0/photos/108244876431105742323/albums/6029631260384977873/6029631269719723986?pid=6029631269719723986&oid=108244876431105742323

I cannot reproduce this on demand.  I am currently trying patch #2 and will
report if I see impossible msc times.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-06-28 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 12:52 [Bug 79051] New: Panic with radeon hd 5750, bisected bugzilla-daemon
2014-06-27 21:06 ` [Bug 79051] " bugzilla-daemon
2014-06-28 14:02 ` bugzilla-daemon [this message]
2014-07-11 16:32 ` 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-79051-2300-7SF7vYG6n1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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