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 36812] GPU lockup in Team Fortress 2
Date: Mon, 16 May 2011 12:47:38 -0700 (PDT)	[thread overview]
Message-ID: <20110516194739.87C7E13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36812-502@http.bugs.freedesktop.org/>

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

--- Comment #3 from Sven Arvidsson <sa@whiz.se> 2011-05-16 12:47:38 PDT ---
I'm having the same problem with Left 4 Dead on:

System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: REDWOOD
-- Model: XFX Radeon HD 5670 1GB
-- Display connector: DVI
-- xf86-video-ati: 6.14.1
-- xserver: 1.10.1
-- mesa: git-51095f7
-- drm: 2.4.25
-- kernel: 2.6.39-rc7

Reverting the commit mentioned above works.

The apitrace uploaded here might be useful to reproduce the hang:
http://dl.dropbox.com/u/28577999/l4d.trace.7z

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

  parent reply	other threads:[~2011-05-16 19:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 18:36 [Bug 36812] New: GPU lockup in Team Fortress 2 bugzilla-daemon
2011-05-03 18:46 ` [Bug 36812] " bugzilla-daemon
2011-05-16 19:45 ` bugzilla-daemon
2011-05-16 19:47 ` bugzilla-daemon [this message]
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=20110516194739.87C7E13004F@annarchy.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).