All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60981] New: dri/r600: severe screen corruption with Radeon HD 6570
Date: Sun, 17 Feb 2013 00:35:35 +0000	[thread overview]
Message-ID: <bug-60981-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1082 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=60981

          Priority: medium
            Bug ID: 60981
          Assignee: dri-devel@lists.freedesktop.org
           Summary: dri/r600: severe screen corruption with Radeon HD 6570
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: steve@steve-m.de
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/DRI/R600
           Product: Mesa

Created attachment 74957
  --> https://bugs.freedesktop.org/attachment.cgi?id=74957&action=edit
lspci, xorg log and glxinfo

With my VTX3D Radeon HD 6570 card the entire screen content is corrupted, see
the images and video. The proprietary AMD driver works fine.
This problem is nothing new, I've seen it since I got the card with Ubuntu
12.04, 12.10 and now 13.04 (+xorg-edgers-ppa).

http://steve-m.de/pics/radeon_artifacts.png
http://steve-m.de/pics/radeon_corruption.ogv

Also see the attached logfiles.

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

[-- Attachment #1.2: Type: text/html, Size: 2654 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-02-17  0:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17  0:35 bugzilla-daemon [this message]
2013-02-17 16:04 ` [Bug 60981] dri/r600: severe screen corruption with Radeon HD 6570 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-60981-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.