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: Thu, 28 Nov 2013 05:34:25 +0000 [thread overview]
Message-ID: <bug-65911-2300-GpczSPKDQy@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 #9 from tomka <tom@voodoo-arts.net> ---
Thanks for the clarification. I just tested different versions of the userspace
tools---unfortunately, without any success. For every component tested, I made
sure the others are used in their resent stable version.
libdrm-git with the current master and
c6d73cfeeaff9596c735d0a10b248f94b2e1e347
Tue Jul 2 09:24:53 2013 +0100
040f6b015ef7d9c1bda09f78a8873f6da45d5e95 (first this year)
Thu May 9 12:55:42 2013 +1000
2089a0080edb1b42449ee9a97f2cef7399c16d53
Mon Nov 5 22:21:42 2012 +0000
xf86-video-ati-git with current master and
67fb82a3f0759b171fea21b475a70fa825693570
Tue Oct 1 09:35:30 2013 -0400
fdb7563a5cbc736b09c2864b67a93b475c98b2bd
Thu Jan 24 21:17:11 2013 -0500
4e35b2f530e2ca8c7b7220cacd05c661de43d20d
Thu Jan 10 12:10:52 2013 +0100
60cd6ceaf44b506433aebf6b3a639a17604dfddd
Wed Nov 21 18:42:56 2012
mesa-git (and thereby mesa-libgl-git and ati-dri-gitwith current master and
e556286802811b4b99c692d1ff5197f8ee1f011b
Wed Mar 20 11:54:33 2013 -0700
5ffa28df4e4cc22481b4ed41c78632f35765f41d
Wed Jul 31 15:18:52 2013 +0200
For mesa-git, I couldn't get further back in history easily, because Bison 3
wasn't supported before. Like I said, no change couldn't fix the GPU lockups or
even change the error itself. During the tests, however, I figured there was
slightly more detail in the dmesg log which I didn't see before:
kernel: radeon 0000:00:01.0: GPU lockup CP stall f...ec
kernel: radeon 0000:00:01.0: GPU lockup (waiting f...2)
kernel: [drm:r600_ib_test] *ERROR* radeon: fence w...).
kernel: [drm:radeon_ib_ring_tests] *ERROR* radeon:...).
kernel: radeon 0000:00:01.0: ib ring test failed (-35).
Do you have any suggestions on what I could try next?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-11-28 5:34 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 [this message]
2013-11-29 6:14 ` bugzilla-daemon
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-GpczSPKDQy@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