dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79659] New: R9 270X lockup with unigine valley since radeonsi: enable ARB_sample_shading
Date: Wed, 04 Jun 2014 22:58:51 +0000	[thread overview]
Message-ID: <bug-79659-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 8769 bytes --]

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

          Priority: medium
            Bug ID: 79659
          Assignee: dri-devel@lists.freedesktop.org
           Summary: R9 270X lockup with unigine valley since radeonsi:
                    enable ARB_sample_shading
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: adf.lists@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

R9 270X since -

commit f98a7d89be5d307c7a80fbde028a610f4377c3b9
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Wed May 7 13:15:41 2014 +0200

    radeonsi: enable ARB_sample_shading

unigine valley run like -

vblank_mode=0 MESA_GLSL_VERSION_OVERRIDE=330 MESA_GL_VERSION_OVERRIDE=3.3
./valley

will gpu lock then hard lock if I don't sysrq sub quickly enough 

Jun  4 21:59:31 ph4 kernel: radeon 0000:01:00.0: ring 3 stalled for more than
10003msec
Jun  4 21:59:31 ph4 kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x000000000000d8a9 last fence id 0x000000000000d8a7 on ring 3)
Jun  4 21:59:31 ph4 kernel: radeon 0000:01:00.0: failed to get a new IB (-35)
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0: Saved 1677 dwords of commands
on ring 0.
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0: GPU softreset: 0x0000004D
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS               =
0xF7D20028
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0           =
0xEC400000
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1           =
0xEDC00000
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS               =
0x200400C0
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS2              =
0x00000000
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 =
0x00000000
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 =
0x40000000
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     =
0x00008006
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   R_008680_CP_STAT          =
0x80228647
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   =
0x44483106
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   =
0x44C83D57
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jun  4 21:59:32 ph4 kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS               =
0x00003028
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0           =
0x00000006
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1           =
0x00000006
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS               =
0x200400C0
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS2              =
0x00000000
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 =
0x00000000
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 =
0x00000000
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     =
0x00000000
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   R_008680_CP_STAT          =
0x00000000
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   =
0x44C83D57
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   =
0x44C83D57
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to
resume
Jun  4 21:59:33 ph4 kernel: [drm] probing gen 2 caps for device 1022:9603 =
300d02/0
Jun  4 21:59:33 ph4 kernel: [drm] PCIE gen 2 link speeds already enabled
Jun  4 21:59:33 ph4 kernel: [drm] PCIE GART of 1024M enabled (table at
0x0000000000276000).
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: WB enabled
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu
addr 0x0000000080000c00 and cpu addr 0xffff8800cc194c00
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu
addr 0x0000000080000c04 and cpu addr 0xffff8800cc194c04
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu
addr 0x0000000080000c08 and cpu addr 0xffff8800cc194c08
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu
addr 0x0000000080000c0c and cpu addr 0xffff8800cc194c0c
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu
addr 0x0000000080000c10 and cpu addr 0xffff8800cc194c10
Jun  4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu
addr 0x0000000000075a18 and cpu addr 0xffffc900105b5a18
Jun  4 21:59:33 ph4 kernel: [drm] ring test on 0 succeeded in 3 usecs
Jun  4 21:59:33 ph4 kernel: [drm] ring test on 1 succeeded in 1 usecs
Jun  4 21:59:33 ph4 kernel: [drm] ring test on 2 succeeded in 1 usecs
Jun  4 21:59:33 ph4 kernel: [drm] ring test on 3 succeeded in 2 usecs
Jun  4 21:59:33 ph4 kernel: [drm] ring test on 4 succeeded in 1 usecs
Jun  4 21:59:33 ph4 kernel: [drm] ring test on 5 succeeded in 2 usecs
Jun  4 21:59:33 ph4 kernel: [drm] UVD initialized successfully.
Jun  4 21:59:43 ph4 kernel: radeon 0000:01:00.0: ring 0 stalled for more than
10000msec
Jun  4 21:59:43 ph4 kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x000000000002dc5a last fence id 0x000000000002dc3f on ring 0)
Jun  4 21:59:43 ph4 kernel: [drm:r600_ib_test] *ERROR* radeon: fence wait
failed (-35).
Jun  4 21:59:43 ph4 kernel: [drm:radeon_ib_ring_tests] *ERROR* radeon: failed
testing IB on GFX ring (-35).
Jun  4 21:59:43 ph4 kernel: radeon 0000:01:00.0: ib ring test failed (-35).
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GPU softreset: 0x00000048
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS               =
0xA0003028
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0           =
0x00000006
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1           =
0x00000006
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS               =
0x200400C0
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS2              =
0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 =
0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 =
0x00010000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     =
0x00400002
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_008680_CP_STAT          =
0x84010243
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   =
0x44C83D57
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   =
0x44C83D57
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jun  4 21:59:44 ph4 kernel: SysRq : Emergency Sync
Jun  4 21:59:44 ph4 kernel: Emergency Sync complete
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS               =
0x00003028
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0           =
0x00000006
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1           =
0x00000006
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS               =
0x200400C0
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   SRBM_STATUS2              =
0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 =
0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 =
0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     =
0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_008680_CP_STAT          =
0x00000000
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   =
0x44C83D57
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   =
0x44C83D57
Jun  4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to
resume

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 10212 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-06-04 22:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 22:58 bugzilla-daemon [this message]
2014-06-05  7:35 ` [Bug 79659] R9 270X lockup with unigine valley since radeonsi: enable ARB_sample_shading bugzilla-daemon
2014-06-05 18:50 ` bugzilla-daemon
2014-06-05 22:52 ` bugzilla-daemon
2014-06-06  3:03 ` bugzilla-daemon
2014-06-11  0:05 ` bugzilla-daemon
2014-06-11  2:20 ` bugzilla-daemon
2014-06-11  9:50 ` bugzilla-daemon
2014-06-11  9:58 ` bugzilla-daemon
2014-07-11 14:49 ` bugzilla-daemon
2014-07-11 16:21 ` bugzilla-daemon
2014-07-13 18:05 ` bugzilla-daemon
2014-07-18 13:12 ` bugzilla-daemon
2014-07-18 21:59 ` bugzilla-daemon
2014-10-08 13:18 ` bugzilla-daemon
2014-10-09  6:08 ` bugzilla-daemon
2014-10-09  8:35 ` bugzilla-daemon
2014-10-09 13:25 ` bugzilla-daemon
2014-10-10 16:30 ` bugzilla-daemon
2014-11-11  2:41 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-79659-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox