All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65911] New: radeon: garbled output/only noise through HDMI and GPU lockups
Date: Wed, 27 Nov 2013 04:00:14 +0000	[thread overview]
Message-ID: <bug-65911-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=65911

            Bug ID: 65911
           Summary: radeon: garbled output/only noise through HDMI and GPU
                    lockups
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.12.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: tom@voodoo-arts.net
        Regression: No

Created attachment 116301
  --> https://bugzilla.kernel.org/attachment.cgi?id=116301&action=edit
dmesg 3.12.1 with radeon.audio=1

Hi, I am not able to start X on computer with an ATI Radeon HD 7540D graphics
card through HDMI running the linux 3.12.1 kernel. I also tried with 3.10.10
which didn't change anything. I can see my TTY without any problems, though.
Starting X however gives me a totally messed up sceen without any structure or
information---is is basically color noise. Here and there a black or blue
block, but in general it is noise.

Looking at the logs, I can see that there are GPU lockups after which X resets
it. This happens indenpently of me setting radeon.audio=1 or 0. However, I've
attached a dmesg output with radeon.audio=1 and with radeon.audio=0.

After a couple of GPU lockups the kernel will eventually panic. This is the top
of the callstack:

Call Trace:
 <IRQ>
 ? __wake_up
 drm_send_vblank_event [drm]
 radeon_crtc_handle_flip [radeon]
 evergreen_irq_process [radeon]

I've see issues #60709 and #60687, but the fix posted there is already in my
kernel and aparantly doesn't fix my issue. I also tried something suggested in
#60687: hdmi regset 0x12c44 0x00000033

With radeon.audio=0, before I try to start X:
OLD: 0x12c44 (12c44)    0x00000033 (51)
NEW: 0x12c44 (12c44)    0x00000033 (51)

With radeon.audio=0, after I have started X:
OLD: 0x12c44 (12c44)    0x00000000 (0)
NEW: 0x12c44 (12c44)    0x00000033 (51)

With radeon.audio=1, before I try to start X:
OLD: 0x12c44 (12c44)    0x00000000 (0)
NEW: 0x12c44 (12c44)    0x00000033 (51)

With radeon.audio=1, after I have started X:
OLD: 0x12c44 (12c44)    0x00000033 (51)
NEW: 0x12c44 (12c44)    0x00000033 (51)

All this, however, didn't change anything.

If readeon.audio=1 is set, I can play audio over HDMI until there a GPU lockup
and again after the GPU reset.

I've also tried radeon options dpm and no_wb without any success. It also
didn't help to add 'Option "AccelMethod" "EXA"' to the radeon driver/device
section in /etc/X11/xorg.conf.d/20-radeon.conf.

Are there more things I could test or provide?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2013-11-27  4:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  4:00 bugzilla-daemon [this message]
2013-11-27  4:00 ` [Bug 65911] radeon: garbled output/only noise through HDMI and GPU lockups 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
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@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.