All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66836] New: [r600g] WoW is crashing with HD6450
Date: Thu, 11 Jul 2013 23:14:30 +0000	[thread overview]
Message-ID: <bug-66836-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 66836
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [r600g] WoW is crashing with HD6450
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: rankincj@googlemail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

WoW has started crashing with my Hd6450. A "git bisect" pinpoints this commit:

862f69fbe1e54e0e9a3c439450a14f0319648b60 is the first bad commit
commit 862f69fbe1e54e0e9a3c439450a14f0319648b60
Author: Marek Olšák <maraeo@gmail.com>
Date:   Sun Jun 30 14:57:17 2013 +0200

    r600g: don't call buffer_wait in buffer_mmap_sync_with_rings

    The winsys should do this, because it measures how much time we spend
    in buffer_map doing synchronization, which can be viewed with the gallium
    HUD.

    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>

:040000 040000 7443defc91af969379873fc85698e78cc0731b12
9a18818193c561b6aff233efc290f7655924cbd1 M    src

WoW's own crash dump analysis is attached, but the relevant part appears to be:

--- Thread ID: 74 [Current Thread] ---
00007FEEB939E2AD              radeon_get_reloc+45
(0000000000000000,0000000000000000,0000000000000000,0000000000000000)
00007FEEB939D6C7              radeon_bo_map+551
(0000000000000000,0000000000000000,0000000000000000,0000000000000000)
00007FEEB933C89B              r600_buffer_transfer_map+107
(0000000000000000,0000000000000000,0000000000000000,0000000000000000)
00007FEEB917A0D7              st_bufferobj_get_subdata+119
(0000000000000000,000

(It turns out that I was running WoW in DXD9 mode rather than OpenGL mode, but
it still shouldn't have crashed.)

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

[-- Attachment #1.2: Type: text/html, Size: 3468 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-07-11 23:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 23:14 bugzilla-daemon [this message]
2013-07-11 23:15 ` [Bug 66836] [r600g] WoW is crashing with HD6450 bugzilla-daemon
2013-07-11 23:16 ` bugzilla-daemon
2013-07-13  1:03 ` bugzilla-daemon
2013-07-13 12:12 ` bugzilla-daemon
2013-07-13 12:12 ` 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-66836-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.