dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73110] New: [BISECTED] Serious Sam 3 crashes with R600_LLVM=1 (CAYMAN)
Date: Sun, 29 Dec 2013 08:19:23 +0000	[thread overview]
Message-ID: <bug-73110-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 73110
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [BISECTED] Serious Sam 3 crashes with R600_LLVM=1
                    (CAYMAN)
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: alexandre.f.demers@gmail.com
          Hardware: All
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

More than a week ago, after updating mesa, I began experiencing trouble
launching Serious Sam 3. Bisecting gave me the following:

696229523d919de15ebc25d0f475bf56d7dad4a9 is the first bad commit
commit 696229523d919de15ebc25d0f475bf56d7dad4a9
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Thu Dec 12 18:09:08 2013 +0100

    r600g: use shader-based MSAA resolving when hw-based one cannot be used

    This fixes some MSAA integer tests.

:040000 040000 b04b89764c5edee6dd685e22d47e36a11060583f
147827de9fe4e00bae5cc5844052b4fc45bb396c M    src

However, setting R600_LLVM=0 prevent the crash.

Using an HD6950 (Cayman) on kernel 3.13-rc5 with latest drm and ddx from git on
ArchLinux 64bit.

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

[-- Attachment #1.2: Type: text/html, Size: 2768 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:[~2013-12-29  8:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-29  8:19 bugzilla-daemon [this message]
2013-12-30  6:15 ` [Bug 73110] [BISECTED] commit "r600g: use shader-based MSAA resolving when hw-based one cannot be used" crashes some games with R600_LLVM=1 bugzilla-daemon
2014-01-07  0:51 ` bugzilla-daemon
2014-01-10  0:01 ` bugzilla-daemon
2014-01-10  0:27 ` bugzilla-daemon
2014-01-10  1:25 ` bugzilla-daemon
2014-01-10 17:25 ` bugzilla-daemon
2014-01-10 19:13 ` bugzilla-daemon
2014-01-11  5:50 ` bugzilla-daemon
2014-01-11 10:30 ` bugzilla-daemon
2014-01-11 16:47 ` bugzilla-daemon
2014-01-14  5:32 ` bugzilla-daemon
2014-01-14  5:33 ` [Bug 73110] [BISECTED] commit "r600g: use shader-based MSAA resolving when hw-based one cannot be used" crashes some games when R600_LLVM=1 with LLVM < 3.4 bugzilla-daemon
2014-01-31 23:34 ` bugzilla-daemon
2014-01-31 23:34 ` bugzilla-daemon
2014-01-31 23:43 ` bugzilla-daemon
2014-02-01  7:18 ` bugzilla-daemon
2014-02-03 19:52 ` bugzilla-daemon
2014-02-03 20:25 ` 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-73110-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;
as well as URLs for NNTP newsgroup(s).