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 82019] New: Unreal Engine Effects Cave demo lockup HD 7970M
Date: Fri, 01 Aug 2014 17:18:45 +0000	[thread overview]
Message-ID: <bug-82019-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 82019
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Unreal Engine Effects Cave demo lockup HD 7970M
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: haagch@frickel.club
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 103826
  --> https://bugs.freedesktop.org/attachment.cgi?id=103826&action=edit
full dmesg with lockup

On my ivy bridge/HD 7970M hybrid laptop, started with

DRI_PRIME=1 GALLIUM_HUD="fps,VRAM-usage+GTT-usage" ./Effects
so no hyperz.

mesa git with f4b0ab7afd83c811329211eae8167c9bf238870c reverted because of bug
81834 and with 0001-glsl-support-unsigned-increment-in-ir_loop.patch from
https://bugs.freedesktop.org/show_bug.cgi?id=80880#c10

On reddit someone with a HD 7790 said it works
(http://www.reddit.com/r/linux_gaming/comments/2cbspp/unreal_engine_4_starts_working_on_the_radeonsi/cjdzh2v)

For me with my HD 7970M it produces this hang on both 3.16-rc7 and
agd5f/drm-next-3.17-rebased-on-fixes:

ring 3 stalled for more than 10296msec
GPU lockup (waiting for 0x0000000000000cdc last fence id 0x0000000000000cdb on
ring 3)
scheduling IB failed (-35).
Saved 525 dwords of commands on ring 0.
GPU softreset: 0x0000004D
  GRBM_STATUS               = 0xE7DE5028
  GRBM_STATUS_SE0           = 0xEF800002
  GRBM_STATUS_SE1           = 0xEFC00002
  SRBM_STATUS               = 0x200000C0
  SRBM_STATUS2              = 0x00000000
  R_008674_CP_STALLED_STAT1 = 0x00000000
  R_008678_CP_STALLED_STAT2 = 0x00010800
  R_00867C_CP_BUSY_STAT     = 0x00408006
  R_008680_CP_STAT          = 0x84038647
  R_00D034_DMA_STATUS_REG   = 0x45483106
  R_00D834_DMA_STATUS_REG   = 0x44C83D57
  VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
  VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
GRBM_SOFT_RESET=0x0000DDFF
SRBM_SOFT_RESET=0x00100100
  GRBM_STATUS               = 0x00003028
  GRBM_STATUS_SE0           = 0x00000006
  GRBM_STATUS_SE1           = 0x00000006
  SRBM_STATUS               = 0x200000C0
  SRBM_STATUS2              = 0x00000000
  R_008674_CP_STALLED_STAT1 = 0x00000000
  R_008678_CP_STALLED_STAT2 = 0x00000000
  R_00867C_CP_BUSY_STAT     = 0x00000000
  R_008680_CP_STAT          = 0x00000000
  R_00D034_DMA_STATUS_REG   = 0x44C83D57
  R_00D834_DMA_STATUS_REG   = 0x44C83D57
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: 4511 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-08-01 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 17:18 bugzilla-daemon [this message]
2014-08-01 17:37 ` [Bug 82019] Unreal Engine Effects Cave demo lockup HD 7970M bugzilla-daemon
2014-08-01 17:49 ` bugzilla-daemon
2014-08-13 10:19 ` bugzilla-daemon
2014-08-14 17:23 ` bugzilla-daemon
2014-08-14 18:19 ` 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-82019-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