Bug 76957 - Pixel artifacts and corruption plus system freeze and instabilities with the free radeon driver (AMD HD 6570)
Summary: Pixel artifacts and corruption plus system freeze and instabilities with the ...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-02 17:10 UTC by benjamin.menant+debian
Modified: 2019-11-19 08:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Screenshot (152.70 KB, image/png)
2014-04-02 17:10 UTC, benjamin.menant+debian 		no flags Details
Xorg log (48.72 KB, text/plain)
2014-04-02 17:11 UTC, benjamin.menant+debian 		no flags Details
glxinfo outputs (57.35 KB, text/plain)
2014-04-02 17:12 UTC, benjamin.menant+debian 		no flags Details
dmesg | grep radeon (1.76 KB, text/plain)
2014-04-02 17:14 UTC, benjamin.menant+debian 		no flags Details
lspci -vvnn (30.86 KB, text/plain)
2014-04-02 17:20 UTC, benjamin.menant+debian 		no flags Details
Syslog excerpt showing a segfault (I think it’s related) (682 bytes, text/plain)
2014-04-02 17:21 UTC, benjamin.menant+debian 		no flags Details
full dmesg (55.61 KB, text/plain)
2014-04-02 20:15 UTC, benjamin.menant+debian 		no flags Details
Show Obsolete (1) View All

Description benjamin.menant+debian 2014-04-02 17:10:39 UTC 
Created attachment 96797 [details]
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).
Comment 1 benjamin.menant+debian 2014-04-02 17:11:51 UTC 
Created attachment 96799 [details]
Xorg log
Comment 2 benjamin.menant+debian 2014-04-02 17:12:45 UTC 
Created attachment 96800 [details]
glxinfo outputs
Comment 3 benjamin.menant+debian 2014-04-02 17:14:01 UTC 
Created attachment 96801 [details]
dmesg | grep radeon
Comment 4 benjamin.menant+debian 2014-04-02 17:20:16 UTC 
Created attachment 96802 [details]
lspci -vvnn
Comment 5 benjamin.menant+debian 2014-04-02 17:21:50 UTC 
Created attachment 96803 [details]
Syslog excerpt showing a segfault (I think it’s related)
Comment 6 benjamin.menant+debian 2014-04-02 17:26:45 UTC 
Erratum: my graphic card has 256 MB of RAM.

Thank you,
Benjamin.
Comment 7 Alex Deucher 2014-04-02 18:54:07 UTC 
Please attach your full dmesg output.  This is not related to bug 66932 as dpm is not enabled on your asic by default.
Comment 8 benjamin.menant+debian 2014-04-02 20:15:44 UTC 
Created attachment 96809 [details]
full dmesg
Comment 9 benjamin.menant+debian 2014-04-04 10:37:27 UTC 
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.
Comment 10 Alex Deucher 2014-04-04 12:58:10 UTC 
(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.
Comment 11 benjamin.menant+debian 2014-04-04 13:33:27 UTC 
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.
Comment 12 Alex Deucher 2014-04-04 13:57:56 UTC 
Does disabling tiling help?  Add:
Option "ColorTiling" "False"
Option "ColorTiling2D" "False"
to the device section of your xorg.conf
Comment 13 benjamin.menant+debian 2014-04-04 21:08:32 UTC 
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.
Comment 14 Martin Peres 2019-11-19 08:47:55 UTC 
-- 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.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.