All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94186] Immediate crash when launching World of Warcraft with RV790
Date: Wed, 17 Feb 2016 01:28:14 +0000	[thread overview]
Message-ID: <bug-94186-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 94186
           Summary: Immediate crash when launching World of Warcraft with
                    RV790
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: rankincj@googlemail.com
        QA Contact: dri-devel@lists.freedesktop.org

Warcraft has suddenly started to crash on launch with git Mesa on my RV790.
Bisection has identified this commit:

61ed09c7ea41e559219c772f18ea00942d54d30a is the first bad commit
commit 61ed09c7ea41e559219c772f18ea00942d54d30a
Author: Samuel Pitoiset <samuel.pitoiset@gmail.com>
Date:   Mon Jan 4 23:56:08 2016 +0100

    gallium/cso: add support for compute shaders

    Changes from v2:
     - removed cso_{save,restore}_compute_shader() functions and the
       compute_shader_saved variable because disabling compute shaders for
       meta ops is not currently needed

However, I'm not sure I trust bisection here because I have built Mesa from
this revision *twice* and while WoW always crashes with one build, it never
crashes with the other?!

WoW's crash dump only implies that Mesa is trying to read from a null pointer;
I can find no useful stack trace.

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

[-- Attachment #1.2: Type: text/html, Size: 2855 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:[~2016-02-17  1:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  1:28 bugzilla-daemon [this message]
2016-02-17  1:53 ` [Bug 94186] Immediate crash when launching World of Warcraft with RV790 bugzilla-daemon
2016-02-17  9:07 ` bugzilla-daemon
2016-02-17 10:49 ` bugzilla-daemon
2016-02-17 11:40 ` [Bug 94186] Crash when launching glxinfo and " bugzilla-daemon
2016-02-17 16:32 ` bugzilla-daemon
2016-02-17 22:58 ` bugzilla-daemon
2016-02-17 23:22 ` bugzilla-daemon
2016-02-18 19:43 ` bugzilla-daemon
2017-01-25  1:10 ` bugzilla-daemon
2017-01-25  1:10 ` 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-94186-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.