[Bug 62997] New: GPU fault unless R600_DEBUG=nodma

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Apr 1 08:31:59 PDT 2013


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

          Priority: medium
            Bug ID: 62997
          Assignee: dri-devel at lists.freedesktop.org
           Summary: GPU fault unless R600_DEBUG=nodma
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: udovdh at xs4all.nl
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Ever since booting into kernel.org 3.8.4 on my AMD A10-5800K (ARUBA graphics),
running git mesa and git xf86-video-ati, I get short uptimes (15 minutes,
around one hour max) due to crashes.
The logs mention stuff like:

[ 1332.480233] radeon 0000:00:01.0: GPU fault detected: 146 0x0134710c
[ 1332.480243] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000813
[ 1332.480250] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0407100C

Watching youtube `helps` triggering the issue as it appears. (correlates, no
real causation yet) 
Having R600_DEBUG=nodma in the environment solves the problem.

Occasionally I see a GPU lockup, if that is related:

    [29648.098135]  disk 0, wo:0, o:1, dev:sda2
    [29648.098140]  disk 1, wo:0, o:1, dev:sdb2
    [29648.098142]  disk 2, wo:0, o:1, dev:sdc2
    [29648.098145]  disk 3, wo:0, o:1, dev:sdd2
    [68707.166021] radeon 0000:00:01.0: GPU fault detected: 146 0x0d4c2604
    [68707.166030] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x000008D4
    [68707.166043] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C026004
    [70621.378798] radeon 0000:00:01.0: GPU fault detected: 146 0x013c710c
    [70621.378808] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000813
    [70621.378815] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C07100C
    [70621.378837] radeon 0000:00:01.0: GPU fault detected: 147 0x0f0c7102
    [70621.378843] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
    [70621.378848] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
    [70621.378854] radeon 0000:00:01.0: GPU fault detected: 147 0x0f1c7102
    [70621.378859] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
    [70621.378864] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
    [70631.857918] radeon 0000:00:01.0: GPU lockup CP stall for more than
10000msec
    [70631.857927] radeon 0000:00:01.0: GPU lockup (waiting for
0x00000000007e1fe5 last fence id 0x00000000007e1fe3)
    [70631.858436] radeon 0000:00:01.0: sa_manager is not empty, clearing
anyway
    [70631.859755] radeon 0000:00:01.0: Saved 951 dwords of commands on ring 0.
    [70631.859761] radeon 0000:00:01.0: GPU softreset: 0x00000003
    [70631.859766] radeon 0000:00:01.0:   VM_CONTEXT0_PROTECTION_FAULT_ADDR  
0x00000000
    [70631.859770] radeon 0000:00:01.0:   VM_CONTEXT0_PROTECTION_FAULT_STATUS
0x00000000
    [70631.859774] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
    [70631.859778] radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
    [70631.867299] radeon 0000:00:01.0:   GRBM_STATUS               =
0xA2703828
    [70631.867305] radeon 0000:00:01.0:   GRBM_STATUS_SE0           =
0x1D000007
    [70631.867309] radeon 0000:00:01.0:   GRBM_STATUS_SE1           =
0x00000007
    [70631.867313] radeon 0000:00:01.0:   SRBM_STATUS               =
0x20000040
    [70631.867317] radeon 0000:00:01.0:   R_008674_CP_STALLED_STAT1 =
0x00000000
    [70631.867321] radeon 0000:00:01.0:   R_008678_CP_STALLED_STAT2 =
0x00018000
    [70631.867325] radeon 0000:00:01.0:   R_00867C_CP_BUSY_STAT     =
0x00008006
    [70631.867328] radeon 0000:00:01.0:   R_008680_CP_STAT          =
0x80038647
    [70631.867332] radeon 0000:00:01.0:   GRBM_SOFT_RESET=0x0000DF7B
    [70631.867386] radeon 0000:00:01.0:   GRBM_STATUS               =
0x00003828
    [70631.867390] radeon 0000:00:01.0:   GRBM_STATUS_SE0           =
0x00000007
    [70631.867393] radeon 0000:00:01.0:   GRBM_STATUS_SE1           =
0x00000007
    [70631.867397] radeon 0000:00:01.0:   SRBM_STATUS               =
0x20000040
    [70631.867400] radeon 0000:00:01.0:   R_008674_CP_STALLED_STAT1 =
0x00000000
    [70631.867404] radeon 0000:00:01.0:   R_008678_CP_STALLED_STAT2 =
0x00000000
    [70631.867408] radeon 0000:00:01.0:   R_00867C_CP_BUSY_STAT     =
0x00000000
    [70631.867411] radeon 0000:00:01.0:   R_008680_CP_STAT          =
0x00000000
    [70631.883681] radeon 0000:00:01.0: GPU reset succeeded, trying to resume
    [70631.916445] [drm] PCIE GART of 512M enabled (table at
0x0000000000040000).
    [70631.916534] radeon 0000:00:01.0: WB enabled
    [70631.916536] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000030000c00 and cpu addr 0xffff880235891c00
    [70631.916538] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr
0x0000000030000c04 and cpu addr 0xffff880235891c04
    [70631.916540] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr
0x0000000030000c08 and cpu addr 0xffff880235891c08
    [70631.916541] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr
0x0000000030000c0c and cpu addr 0xffff880235891c0c
    [70631.916543] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr
0x0000000030000c10 and cpu addr 0xffff880235891c10
    [70631.935206] [drm] ring test on 0 succeeded in 3 usecs
    [70631.935264] [drm] ring test on 3 succeeded in 2 usecs
    [70631.935271] [drm] ring test on 4 succeeded in 1 usecs
    [70631.949531] [drm] ib test on ring 0 succeeded in 0 usecs
    [70631.950057] [drm] ib test on ring 3 succeeded in 0 usecs
    [70631.950576] [drm] ib test on ring 4 succeeded in 1 usecs

-- 
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/20130401/b6fc6f8d/attachment.html>


More information about the dri-devel mailing list