All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26043] New: Graphics corruption in Sauerbraten
Date: Thu, 14 Jan 2010 08:06:43 -0800 (PST)	[thread overview]
Message-ID: <bug-26043-502@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=26043

           Summary: Graphics corruption in Sauerbraten
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
               URL: http://jon.severinsson.net/mesa/screenshot_10399.png
        OS/Version: Linux (All)
            Status: NEW
          Keywords: patch, regression
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: jon@severinsson.net


Created an attachment (id=32638)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=32638)
Uggly patch that fixes the problem for me

After upgrading from Mesa 7.6.1 to Mesa 7.7 Sauerbraten would display severe
graphics corruptions on screen making the game unplayable (see URL for a
screenshot).

I recently had some time to spare and decided to try to hunt down the
regression as an exercise in learning git, and managed to create the attached
patch that solves the problem for me.

Please note that the patch isn't really a fix, more of a workaround, as it
replaces 96 lines of new code with 206 lines of old code from the git history,
rather than fixing the new code, but it works for me, and perhaps it can serve
as a starting point for someone more knowledgeable to fix it for real.

The patch was originally created by going through git history between
mesa_7_6_1 and mesa_7_7 looking for commits that broke something, and merging
everything but those commits to a new tree. The commits I skipped was eea30906
614e8f22 fc38a3cf 45eb9d2f 5f7d5d3e 57864f6e 731810f8 and 66d6f9e8. I also had
to do some manual conflict resolution when merging other commits. I then took
the difference between mesa_7_7 and the new tree to create a patch that fixed
Sauerbraten. Finally I cleaned up the patch and removed anything that wasn't
necessary to get Sauerbraten working, giving me the attached patch.

`lspci -v` output for my card:
01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600
Series] (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 01bc
        Flags: bus master, fast devsel, latency 0, IRQ 18
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at fdfe0000 (64-bit, non-prefetchable) [size=64K]
        I/O ports at ee00 [size=256]
        [virtual] Expansion ROM at fdf00000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information <?>
        Kernel driver in use: radeon


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

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
--

             reply	other threads:[~2010-01-14 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 16:06 bugzilla-daemon [this message]
2010-01-14 17:02 ` [Bug 26043] Graphics corruption in Sauerbraten bugzilla-daemon
2010-03-29 10:58 ` bugzilla-daemon
2011-11-13 17:05 ` 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-26043-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.