From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65911] radeon: garbled output/only noise through HDMI and GPU lockups
Date: Fri, 29 Nov 2013 06:14:50 +0000 [thread overview]
Message-ID: <bug-65911-2300-Wk69wSCYnY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65911-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65911
--- Comment #10 from tomka <tom@voodoo-arts.net> ---
Oops, I figured the last dmesg log lines were truncated. Here they are again:
[ 170.607701] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec
[ 170.607711] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000000007
last fence id 0x0000000000000002)
[ 170.607717] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
[ 170.607723] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
GFX ring (-35).
[ 170.607727] radeon 0000:00:01.0: ib ring test failed (-35).
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-11-29 6:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 4:00 [Bug 65911] New: radeon: garbled output/only noise through HDMI and GPU lockups bugzilla-daemon
2013-11-27 4:00 ` [Bug 65911] " bugzilla-daemon
2013-11-27 4:01 ` bugzilla-daemon
2013-11-27 4:01 ` bugzilla-daemon
2013-11-27 4:01 ` bugzilla-daemon
2013-11-27 4:03 ` bugzilla-daemon
2013-11-27 5:37 ` bugzilla-daemon
2013-11-27 14:41 ` bugzilla-daemon
2013-11-27 14:58 ` bugzilla-daemon
2013-11-28 5:34 ` bugzilla-daemon
2013-11-29 6:14 ` bugzilla-daemon [this message]
2013-11-29 23:55 ` bugzilla-daemon
2013-11-30 0:35 ` bugzilla-daemon
2013-11-30 1:24 ` bugzilla-daemon
2013-11-30 2:29 ` 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-65911-2300-Wk69wSCYnY@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.