All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36812] New: GPU lockup in Team Fortress 2
Date: Tue,  3 May 2011 11:36:23 -0700 (PDT)	[thread overview]
Message-ID: <bug-36812-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: GPU lockup in Team Fortress 2
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: Enrico_m@gmx.de


After updating mesa to current git I always get a GPU lockup when the game is
about to start. After git bisect I got the following commit:

commit 18dcbd358f1d4fd5e4a40fa26c6d3bf99485884e
Author: Tom Stellard <tstellar@gmail.com>
Date:   Sun Mar 27 01:17:43 2011 -0700

    prog_optimize: Fix reallocating registers for shaders with loops

    Registers that are used inside of loops need to be considered live
    starting with the first instruction of the outermost loop.

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

    NOTE: This is a candidate for the 7.9 and 7.10 branches.

    Reviewed-by: Eric Anholt <eric@anholt.net>


tested with kernels:
2.6.37.4
2.6.38.4
2.6.39-RC5

This is the call trace:

WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 0xffffffff812dc0ba()

[<ffffffff8103e2aa>] <warn_slowpath_common+7a/b0>
[<ffffffff8103e381>] <warn_slowpath_fmt+41/50>
[<ffffffff812dc0ba>] <radeon_fence_wait+35a/3c0>
[<ffffffff81059fc0>] <autoremove_wake_function+0/40>
[<ffffffff81037a41>] <get_parent_ip+11/50>
[<ffffffff812dc92c>] <radeon_sync_obj_wait+c/10>
[<ffffffff812a461f>] <ttm_bo_wait+ff/1c0>
[<ffffffff81037a41>] <get_parent_ip+11/50>
[<ffffffff812f49c1>] <radeon_gem_wait_idle_ioctl+91/110>
[<ffffffff8128f80b>] <drm_ioctl+3fb/4a0>
[<ffffffff812f4930>] <radeon_gem_wait_idle_ioctl+0/110>
[<ffffffff810386bd>] <sub_preempt_count+9d/d0>
[<ffffffff81476791>] <_raw_spin_unlock_irq+11/40>
[<ffffffff810022bd>] <do_signal+17d/7b0>
[<ffffffff8100b5ec>] <fpu_finit+1c/30>
[<ffffffff810f00cb>] <do_vfs_ioctl+9b/4f0>
[<ffffffff810386bd>] <sub_preempt_count+9d/d0>
[<ffffffff81002bcc>] <sys_rt_sigreturn+22c/240>
[<ffffffff810f056a>] <sys_ioctl+4a/80>
[<ffffffff8147747b>] <system_call_fastpath+16/1b>

glxinfo (with mesa at git head):
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 7.11-devel (git-a8bbce8)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-05-03 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 18:36 bugzilla-daemon [this message]
2011-05-03 18:46 ` [Bug 36812] GPU lockup in Team Fortress 2 bugzilla-daemon
2011-05-16 19:45 ` bugzilla-daemon
2011-05-16 19:47 ` bugzilla-daemon
2011-05-18  4:21 ` bugzilla-daemon
2011-05-19 18:16 ` bugzilla-daemon
2011-05-30 13:47 ` bugzilla-daemon
2011-05-31  9:21 ` bugzilla-daemon
2011-06-02 17:15 ` bugzilla-daemon
2011-06-03 20:54 ` bugzilla-daemon
2011-06-11 17:35 ` bugzilla-daemon
2011-06-13 22: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-36812-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.