From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36542] New: Radeon HD 6570 GPU lockup (waiting for 0x00000281 last fence id 0x00000280)
Date: Sun, 24 Apr 2011 06:18:33 -0700 (PDT) [thread overview]
Message-ID: <bug-36542-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36542
Summary: Radeon HD 6570 GPU lockup (waiting for 0x00000281 last
fence id 0x00000280)
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: Michael@phoronix.com
Created an attachment (id=46018)
--> (https://bugs.freedesktop.org/attachment.cgi?id=46018)
dmesg on lockup
Alex,
Here's the dmesg output I just hit when trying the latest mainline kernel from
24 April on the Radeon HD 6570... I didn't check to see if it's similar to the
lockups I've previously talked about for HD 6570 / HD 6850 in a slightly older
kernel before the latest DRM merge. For this log attached, the GPU locked up
right after starting the GNOME desktop with Compiz, soft reset, and recovered.
Running Mesa Git master as of this morning.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-24 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 13:18 bugzilla-daemon [this message]
2011-04-24 13:47 ` [Bug 36542] Radeon HD 6570 GPU lockup (waiting for 0x00000281 last fence id 0x00000280) bugzilla-daemon
2011-04-24 13:48 ` bugzilla-daemon
2011-04-24 14:40 ` bugzilla-daemon
2011-05-12 21:23 ` bugzilla-daemon
2011-05-26 1:24 ` bugzilla-daemon
2011-05-26 1:32 ` bugzilla-daemon
2011-06-16 14:45 ` bugzilla-daemon
2011-06-25 17:55 ` bugzilla-daemon
2011-06-25 19:31 ` bugzilla-daemon
2011-06-25 22:13 ` bugzilla-daemon
2011-06-28 15:48 ` 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-36542-502@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 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.