Bug 49792

Summary: Pixel noise on the screen
Product: xorg Reporter: Vladislav <ccvs>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: high CC: florian, fredericg_99
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Fix backend map none

Description Vladislav 2012-05-11 05:26:42 UTC
When I load module radeon with modeset=1, I see pixel noise on the screen and some characters from framebuffer console.

If after this I load X, nothing changes.

Videocard HD6570. I have tried kernels 3.2 - 3.3.4.

md5sum TURKS_*
158f8e21ccf228ef063888c4f637fbf0  TURKS_mc.bin
8012e24b187c6b1ba17fa48691c3b048  TURKS_me.bin
25f26ba407a9bb13528b903c617209c8  TURKS_pfp.bin

If I use modeset=0, I don't have KMS and can not start X.
Comment 1 Alex Deucher 2012-05-11 07:56:14 UTC
This is a duplicate of:
https://bugzilla.kernel.org/show_bug.cgi?id=43207
Comment 2 Jerome Glisse 2012-05-24 12:13:52 UTC
Created attachment 62070 [details] [review]
Fix backend map

This patch should fix your issue.
Comment 3 Alex Deucher 2012-06-08 12:30:04 UTC
*** Bug 50891 has been marked as a duplicate of this bug. ***
Comment 4 Goulou 2012-06-08 15:31:01 UTC
I applied the patch, but it did not solve the issue.

I am not 100% sure I applied correctly (it's the first time I did this...), but I followed the instructions from http://fedoraproject.org/wiki/Building_a_custom_kernel so I think I'm quite confident.

Reminder : my bug was #50891
Comment 5 Goulou 2012-06-08 15:33:57 UTC
I forgot to mention that I received the following errors on the console :
 [   35.086959] radeon 0000:01:00.0: GPU lockup CP stall for more than 10020msec
 [   35.086968] GPU lockup (waiting for 0x00000003 last fence id 0x00000001)
 [   35.088218] radeon 0000:01:00.0: GPU softreset 
 [   35.088225] radeon 0000:01:00.0:   GRBM_STATUS=0xB1403828
 [   35.088232] radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x28000007
 [   35.088238] radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000007
 [   35.088245] radeon 0000:01:00.0:   SRBM_STATUS=0x200000C0
 [   35.088262] radeon 0000:01:00.0:   GRBM_SOFT_RESET=0x00007F6B
 [   35.088370] radeon 0000:01:00.0:   GRBM_STATUS=0x00003828
 [   35.088376] radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x00000007
 [   35.088382] radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000007
 [   35.088388] radeon 0000:01:00.0:   SRBM_STATUS=0x200000C0
 [   35.089395] radeon 0000:01:00.0: GPU reset succeed
 [   35.170461] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
 [   35.170621] radeon 0000:01:00.0: WB enabled
 [   35.170635] [drm] fence driver on ring 0 use gpu addr 0x40000c00 and cpu addr 0xffff880425ddbc00
 [   35.186909] [drm] ring test on 0 succeeded in 1 usecs
 [   35.186961] [drm] ib test on ring 0 succeeded in 1 usecs
 [   46.187682] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
Comment 6 Goulou 2012-06-13 00:46:57 UTC
Hi all, 

I checked the source tree where my kernel was built from, and I can confirm that the patch was actually correctly applied...
I'll be very happy to help, if there is anything I can do to help fixing this bug! (some more logs, tests, patches...)

Goulou.
Comment 7 Florian Mickler 2012-07-01 03:52:07 UTC
A patch referencing this bug report has been merged in Linux v3.5-rc1:

commit 95c4b23ec4e2fa5604df229ddf134e31d7b3b378
Author: Jerome Glisse <jglisse@redhat.com>
Date:   Thu May 31 19:00:24 2012 -0400

    drm/radeon: fix HD6790, HD6570 backend programming
Comment 8 Goulou 2012-07-01 13:52:12 UTC
The patch alone did not seem to work, but I'm now running kernel 3.5.0-rc4 (rpm from Fedora 18, installed on F17), and I can confirm that, for the first time ever, the radeon driver works for me!!

As of now, it seems pretty slow thought, but I will check again later : the reboot harmed my raid and it is re-syncing now...

Anyway, at least I'm running a really free driver :-)
Comment 9 Martin Peres 2019-11-19 07:33:43 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/xorg/driver/xf86-video-ati/issues/29.

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.