[Bug 66945] New: Heavy artifacts and unusable graphics system with the latest DPM changes

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jul 15 17:57:49 PDT 2013


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

          Priority: medium
            Bug ID: 66945
          Assignee: dri-devel at lists.freedesktop.org
           Summary: Heavy artifacts and unusable graphics system with the
                    latest DPM changes
          Severity: blocker
    Classification: Unclassified
                OS: Linux (All)
          Reporter: tobi at slackeee.de
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

Using the latest drm-fixes-3.11 and drm-next-3.11 I get heavy artifacts as soon
as the radeon module is loaded, leaving my system unusable. Only the graphics
system stops to work, SSH connections to the system still work.

Hardware: Radeon HD6870 (01:00.0 VGA compatible controller: Advanced Micro
Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series])
Software: Slackware -current

I got these error messages from dmesg:
[   26.514278] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[   26.514291] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004
last fence id 0x0000000000000001)
[   26.649947] radeon 0000:01:00.0: Saved 119 dwords of commands on ring 0.
[   26.649969] radeon 0000:01:00.0: GPU softreset: 0x00000008
[   26.649977] radeon 0000:01:00.0:   GRBM_STATUS               = 0xA0003828
[   26.649983] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[   26.649989] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[   26.649994] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[   26.649999] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[   26.650004] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[   26.650010] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00004100
[   26.650015] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00020180
[   26.650020] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80028042
[   26.650026] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[   26.661433] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00004001
[   26.661490] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[   26.662652] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003828
[   26.662657] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[   26.662663] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[   26.662668] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[   26.662673] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[   26.662679] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[   26.662684] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[   26.662689] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[   26.662694] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[   26.662700] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[   26.662711] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[   26.686572] radeon 0000:01:00.0: WB enabled
[   26.686581] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff880429b6dc00
[   26.686588] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff880429b6dc0c
[   26.688117] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc900112b2118
[   26.920227] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xCAFEDEAD)

I attach a complete dmesg output and lspci output, If anything else is needed
just ask me and I will do my best to get you the info.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130716/15f046e6/attachment.html>


More information about the dri-devel mailing list