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: Tue, 08 Oct 2013 17:54:50 +0000 [thread overview]
Message-ID: <bug-62721-2300-Fq79i0vHAS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62721-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=62721
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #2 from Alex Deucher <alexdeucher@gmail.com> ---
Please attach your full dmesg output. What GPU is this?
Are you sure cb51bb7107aa040f9779be931e3bd6a7b50e0f69 is the correct commit?
That commit only affects the debugfs output. If you don't access those debugfs
files, that code in question is never called. Did you also happen to update
your userspace drivers (mesa or xf86-video-ati)?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-10-08 17:54 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 [this message]
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
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-Fq79i0vHAS@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;
as well as URLs for NNTP newsgroup(s).