Created attachment 96801 [details]
dmesg | grep radeon
Created attachment 96802 [details]
lspci -vvnn
| What | Removed | Added |
|---|---|---|
| Attachment #96797 mime type | text/plain | image/png |
Created attachment 96803 [details]
Syslog excerpt showing a segfault (I think it=E2=80=99s related)
Please attach your full dmesg output. This is not related to bug 66932 as dpm is not enabled on your asic by default.
| Priority | medium |
|---|---|
| Bug ID | 76957 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | Pixel artifacts and corruption plus system freeze and instabi= lities 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 [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 g= ood FPS. And the virtual consoles remain safe & clean; switching between th= em and X has no effect. The system was stable, without screen corruption when I used the AMD=E2=80= =99s 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.c= gi?id=3D66932> 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).
Created attachment 96799 [details]
Xorg log
| What | Removed | Added |
|---|---|---|
| Attachment #96801 is obsolete | 1 |
Created attachment 96809 [details]
full dmesg
Erratum: my graphic card has 256 MB of RAM. Thank you, Benjamin.
Created attachment 96800 [details]
glxinfo outputs
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 - 0x=
000000007FFFFFFF
> [ 5.343552] [drm] Detected VRAM RAM=3D1024M, BAR=3D256M
1G VRAM seems to be a wrong value, since my graphic card holds only 256MB,
which seems to be seeing as BAR (what=E2=80=99s that stuff?).=20
Anyway, could it be the cause of my problem?
Thank you,
Benjamin.
(In reply to comment #9= ) > The dmesg output reveals these lines: >=20 > > [ 5.343548] radeon 0000:05:00.0: VRAM: 1024M 0x000000000000000= 0 - 0x000000003FFFFFFF (1024M used) > > [ 5.343550] radeon 0000:05:00.0: GTT: 1024M 0x0000000040000000= - 0x000000007FFFFFFF > > [ 5.343552] [drm] Detected VRAM RAM=3D1024M, BAR=3D256M >=20 > 1G VRAM seems to be a wrong value, since my graphic card holds only 25= 6MB, > which seems to be seeing as BAR (what=E2=80=99s that stuff?).=20 >=20 > 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 en= tire amount of vram.
Oups, sorry=E2=80=A6 Indeed, you are right Alex, this board ha= s 1 GB <http://www.club-3d.com/index.php/pr= oducts/reader.en/product/radeon-hd-6570-coolstream-edition.html> Thanks again for the clever explainations. Thus, it was my last guess=E2=80=A6 Is there anything else I can do to find= the origin of this issue? Sincerely, Benjamin.
Does disabling tiling help? Add: Option "ColorTiling" "False" Option "ColorTiling2D" "False" to the device section of your xorg.conf
Unfortunately, deactivating ColorTiling and/or ColorTiling2D h= as no effect. I also tried to set "SwapbuffersWait" to "False".=20 Actually, as far as I remember, I tried to test most of the options availab= le (http://manpages.debian.org/cgi-bin/man.cgi?sektion=3D4&quer= y=3Dradeon) two years ago, when I installed the board. Then, I switched to fglrx-driver. I think it=E2=80=99s not related, but=E2=80=A6 often, X failed to restart f= rom 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).=20 Thanks again, Benjamin.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- 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.