All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102201] [regression, SI] GPU crash in Unigine Valley
Date: Sun, 13 Aug 2017 18:20:05 +0000	[thread overview]
Message-ID: <bug-102201-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 102201
           Summary: [regression, SI] GPU crash in Unigine Valley
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: gr.muench@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 133476
  --> https://bugs.freedesktop.org/attachment.cgi?id=133476&action=edit
dmesg crash log

I get random GPU lockups in Unigine Valley. Sometimes it happens at Test 5 and
sometimes in Test 9. Basically the screen is freezing but music continues
playing. After sometime there is only noise on the screen. The performance went
also down, I saw 57 fps in Test 1 and now only 54 fps.
I also experience something similar during playing Shadow Warrior, in the
Prologue mission, GPU hangs forever.

Bisected this to:
064550238ef0b44e341b2a50c3147f83c2a6d5b0 is the first bad commit
commit 064550238ef0b44e341b2a50c3147f83c2a6d5b0
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Thu Jul 27 02:40:34 2017 +0200

    radeonsi: use CLEAR_STATE to initialize some registers

    Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>

:040000 040000 621668e602ccd2f36299e329b096586baa920ba0
68d43945fde8fbbfad6ae444546a981af2507b03 M      src

During regression testing I faced
https://bugs.freedesktop.org/show_bug.cgi?id=101969 where I saw some serious
corruption of the graphics in Valley so I used this patch to overcome
https://cgit.freedesktop.org/mesa/mesa/commit/?id=b9fc9d3f241758ed8a274be7abf68bf448653508
But its the same issue like in the bug report mentioned above. Seems the patch
hasnt fixed all issues.

Device: AMD TAHITI (DRM 2.50.0 / 4.11.0-1-amd-staging, LLVM 5.0.0) (0x6798)
Radeon HD 7970

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

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

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

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

             reply	other threads:[~2017-08-13 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 18:20 bugzilla-daemon [this message]
2017-08-13 19:08 ` [Bug 102201] [regression, SI] GPU crash in Unigine Valley bugzilla-daemon
2017-08-18 14:04 ` bugzilla-daemon
2017-08-19 11:32 ` 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-102201-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.