dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39617] New: Radeon 5750: GPU Lock up at drivers/gpu/drm/radeon/radeon_fence.c:269
Date: Thu, 28 Jul 2011 06:40:52 -0700 (PDT)	[thread overview]
Message-ID: <bug-39617-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Radeon 5750: GPU Lock up at
                    drivers/gpu/drm/radeon/radeon_fence.c:269
           Product: DRI
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: jeff.raber@gmail.com


Created an attachment (id=49664)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49664)
dmesg output showing the lock up 

I am using the stock kernel in F15 (currently 2.6.38.8-35.fc15).  This crash
occurs anytime I try to play the game Cogs (part of "the Humble Indie Bundle 3"
[1]).

To get the game to run, I had to install a library to provide 'S3TC' support 
(aka GL_EXT_texture_compression_s3tc).  Initially, I installed S2TC [2], but
that resulted in a GPU Lockup.  I then installed "libtxc_dxtn" from the
rpmfusion-free repo, which causes the same GPU lockup.

1: http://www.humblebundle.com/
2: https://github.com/divVerent/s2tc

-- 
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-07-28 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 13:40 bugzilla-daemon [this message]
2011-07-28 13:42 ` [Bug 39617] Radeon 5750: GPU Lock up at drivers/gpu/drm/radeon/radeon_fence.c:269 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-39617-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