[Bug 76957] New: Pixel artifacts and corruption plus system freeze and instabilities with the free radeon driver (AMD HD 6570)
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).
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #1 from benjamin.menant+debian@gmail.com --- Created attachment 96799 --> https://bugs.freedesktop.org/attachment.cgi?id=96799&action=edit Xorg log
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #2 from benjamin.menant+debian@gmail.com --- Created attachment 96800 --> https://bugs.freedesktop.org/attachment.cgi?id=96800&action=edit glxinfo outputs
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #3 from benjamin.menant+debian@gmail.com --- Created attachment 96801 --> https://bugs.freedesktop.org/attachment.cgi?id=96801&action=edit dmesg | grep radeon
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #4 from benjamin.menant+debian@gmail.com --- Created attachment 96802 --> https://bugs.freedesktop.org/attachment.cgi?id=96802&action=edit lspci -vvnn
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #5 from benjamin.menant+debian@gmail.com --- Created attachment 96803 --> https://bugs.freedesktop.org/attachment.cgi?id=96803&action=edit Syslog excerpt showing a segfault (I think it’s related)
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #6 from benjamin.menant+debian@gmail.com --- Erratum: my graphic card has 256 MB of RAM.
Thank you, Benjamin.
https://bugs.freedesktop.org/show_bug.cgi?id=76957
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #96797|text/plain |image/png mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #7 from Alex Deucher agd5f@yahoo.com --- Please attach your full dmesg output. This is not related to bug 66932 as dpm is not enabled on your asic by default.
https://bugs.freedesktop.org/show_bug.cgi?id=76957
benjamin.menant+debian@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #96801|0 |1 is obsolete| |
--- Comment #8 from benjamin.menant+debian@gmail.com --- Created attachment 96809 --> https://bugs.freedesktop.org/attachment.cgi?id=96809&action=edit full dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #9 from benjamin.menant+debian@gmail.com --- The dmesg output reveals these lines:
[ 5.343548] radeon 0000:05:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) [ 5.343550] radeon 0000:05:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF [ 5.343552] [drm] Detected VRAM RAM=1024M, BAR=256M
1G VRAM seems to be a wrong value, since my graphic card holds only 256MB, which seems to be seeing as BAR (what’s that stuff?).
Anyway, could it be the cause of my problem?
Thank you, Benjamin.
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #10 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #9)
The dmesg output reveals these lines:
[ 5.343548] radeon 0000:05:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) [ 5.343550] radeon 0000:05:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF [ 5.343552] [drm] Detected VRAM RAM=1024M, BAR=256M
1G VRAM seems to be a wrong value, since my graphic card holds only 256MB, which seems to be seeing as BAR (what’s that stuff?).
Anyway, could it be the cause of my problem?
Your board has 1 GB of vram. The max BAR size is 256 MB regardless of how much video ram is actually on the card. The BAR is the CPU's aperture to vram. The CPU can only access teh first 256 MB of vram, but the GPU can access the entire amount of vram.
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #11 from benjamin.menant+debian@gmail.com --- Oups, sorry… Indeed, you are right Alex, this board has 1 GB http://www.club-3d.com/index.php/products/reader.en/product/radeon-hd-6570-coolstream-edition.html
Thanks again for the clever explainations.
Thus, it was my last guess… Is there anything else I can do to find the origin of this issue?
Sincerely, Benjamin.
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #12 from Alex Deucher agd5f@yahoo.com --- Does disabling tiling help? Add: Option "ColorTiling" "False" Option "ColorTiling2D" "False" to the device section of your xorg.conf
https://bugs.freedesktop.org/show_bug.cgi?id=76957
--- Comment #13 from benjamin.menant+debian@gmail.com --- Unfortunately, deactivating ColorTiling and/or ColorTiling2D has no effect. I also tried to set "SwapbuffersWait" to "False".
Actually, as far as I remember, I tried to test most of the options available (http://manpages.debian.org/cgi-bin/man.cgi?sektion=4&query=radeon) two years ago, when I installed the board. Then, I switched to fglrx-driver.
I think it’s not related, but… often, X failed to restart from the virtual console (weird pixelized screen or black screen, or nothing at all). I had to reboot the computer to double check the result (and then, I did not see any error in the Xorg log).
Thanks again, Benjamin.
https://bugs.freedesktop.org/show_bug.cgi?id=76957
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #14 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/485.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org