From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62721] GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec...
Date: Thu, 16 Jan 2014 04:25:56 +0000 [thread overview]
Message-ID: <bug-62721-2300-3jtKZDcOdR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62721-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=62721
--- Comment #11 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Andrew Dorney from comment #8)
> I am also having a random lockup problem on my HD6850, with the same CP
> stall error. Running Mesa 10.0.1 and kernel 3.12.6 vanilla with radeon
> driver. Attached lspci and dmesg. I'll boot with DPM disabled for the rest
> of the week and see if that changes it.
This bug is about a GPU hang on an r5xx board. You issue is mostly likely
completely unrelated. You issue looks like it may be a duplicate of bug 68571.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-01-16 4:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 13:03 [Bug 62721] New: GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec bugzilla-daemon
2013-10-08 13:03 ` [Bug 62721] " bugzilla-daemon
2013-10-08 17:54 ` bugzilla-daemon
2013-10-09 3:40 ` bugzilla-daemon
2013-10-09 13:15 ` bugzilla-daemon
2013-10-10 17:12 ` bugzilla-daemon
2013-10-10 17:13 ` bugzilla-daemon
2013-10-14 13:52 ` bugzilla-daemon
2014-01-16 4:14 ` bugzilla-daemon
2014-01-16 4:15 ` bugzilla-daemon
2014-01-16 4:15 ` bugzilla-daemon
2014-01-16 4:25 ` bugzilla-daemon [this message]
2014-01-18 4:28 ` bugzilla-daemon
2014-10-10 12:06 ` bugzilla-daemon
2014-10-10 12:09 ` bugzilla-daemon
2014-10-21 14:28 ` bugzilla-daemon
2014-10-21 14:32 ` bugzilla-daemon
2015-02-17 18:54 ` bugzilla-daemon
2015-02-20 10: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=bug-62721-2300-3jtKZDcOdR@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 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.