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 23:55:52 +0000 [thread overview]
Message-ID: <bug-65911-2300-yA59I3yOaI@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 #11 from tomka <tom@voodoo-arts.net> ---
In another bug report (https://bugzilla.redhat.com/show_bug.cgi?id=990986) it
was suggested to disable glx-tls during build configuration. So I replaced the
line "--enable-glx-tls" with "--disable-glx-tls". However, the GPU lock ups
still happen and I can't start X.
Then I tried setting several environment variables like it was suggested in yet
another bug report (https://bugs.freedesktop.org/show_bug.cgi?id=69728):
Neither R600_DEBUG=nohyperz, R600_DEBUG=nodma, R600_DEBUG=nosb or R600_LLVM=0
did help. Not alone and not combined.
Additionally, I removed the lines "--with-llvm-shared-libs" and
"--enable-gallium-llvm" from the ./configure parameters, because I read in bug
69728 there might be some issues with LLVM. This also didn't change anything
(the binaries got obisously much bigger, though).
The next thing I wanted to try is to disable "the new DMA ring for ttm bo
moves" like suggested by you (Alex) in another thread about GPU lockups
(https://groups.google.com/forum/#!topic/fa.linux.kernel/1_KzqknQn_U). However,
this change seems to be already in the mainline kernel.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-11-29 23:55 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
2013-11-29 23:55 ` bugzilla-daemon [this message]
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-yA59I3yOaI@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.