dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76957] New: Pixel artifacts and corruption plus system freeze and instabilities with the free radeon driver (AMD HD 6570)
Date: Wed, 02 Apr 2014 17:10:39 +0000	[thread overview]
Message-ID: <bug-76957-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 76957
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Pixel artifacts and corruption plus system freeze and
                    instabilities with the free radeon driver (AMD HD
                    6570)
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: benjamin.menant+debian@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 96797
  --> https://bugs.freedesktop.org/attachment.cgi?id=96797&action=edit
Screenshot

Hello,

Each time I tried to use the free radeon drivers with my desktop computer, I
got those corrupted pixels when X starts. The issue effects increase as the
session time grows: more and more artifacts, more and more character
alterations (for instance, Thunderbird is displaying blocks instead of
characters), more and more instabilities (programs ends up by a segmentation
fault, and could eventually lead to a system freeze).

Otherwise, Gnome Shell starts without error. `glxgears` works and returns good
FPS. And the virtual consoles remain safe & clean; switching between them and X
has no effect.

The system was stable, without screen corruption when I used the AMD’s FGLRX
drivers.

How could I fix this issue? Any idea?
This ticket seems quite similar, should I try the proposed patch?
<https://bugs.freedesktop.org/show_bug.cgi?id=66932>

Chipset: AMD Radeon HD 6570 (Turks family) with 512MB dedicated RAM (AFAIR).
CPU: Intel DualCore E6300 with 4GB RAM.
Kernel: Linux 3.13-1-amd64.
And I use the defaut Xorg configuration (i.e. no configuration files).

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

[-- Attachment #1.2: Type: text/html, Size: 3617 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:[~2014-04-02 17:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 17:10 bugzilla-daemon [this message]
2014-04-02 17:11 ` [Bug 76957] Pixel artifacts and corruption plus system freeze and instabilities with the free radeon driver (AMD HD 6570) bugzilla-daemon
2014-04-02 17:12 ` bugzilla-daemon
2014-04-02 17:14 ` bugzilla-daemon
2014-04-02 17:20 ` bugzilla-daemon
2014-04-02 17:21 ` bugzilla-daemon
2014-04-02 17:26 ` bugzilla-daemon
2014-04-02 18:51 ` bugzilla-daemon
2014-04-02 18:54 ` bugzilla-daemon
2014-04-02 20:15 ` bugzilla-daemon
2014-04-04 10:37 ` bugzilla-daemon
2014-04-04 12:58 ` bugzilla-daemon
2014-04-04 13:33 ` bugzilla-daemon
2014-04-04 13:57 ` bugzilla-daemon
2014-04-04 21:08 ` bugzilla-daemon
2019-11-19  8:47 ` 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-76957-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox