All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88456] Brütal Legend lockup
Date: Thu, 15 Jan 2015 12:16:16 +0000	[thread overview]
Message-ID: <bug-88456-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 88456
           Summary: Brütal Legend lockup
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: geecko.dev@free.fr

When testing on my desktop PC about two weeks ago, with latest mesa-git and
llvm-git, I was getting a GPU lockup after the intro, when beating up the three
druids. Arch Linux, HD 7950

I tried without HyperZ and with the lowest visual settings but it doesn't
change anything.

Here's an apitrace that makes my computer hang: http://ge.tt/7RmQXf72/v/0?c
(fullscreen 1920x1080)

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

[-- Attachment #1.2: Type: text/html, Size: 2229 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:[~2015-01-15 12:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 12:16 bugzilla-daemon [this message]
2015-01-23  9:37 ` [Bug 88456] Brütal Legend lockup bugzilla-daemon
2015-01-23 10:47 ` bugzilla-daemon
2015-01-25 12:25 ` bugzilla-daemon
2015-01-30 16:11 ` bugzilla-daemon
2015-01-31  0:49 ` bugzilla-daemon
2015-01-31  8:29 ` 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-88456-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.