All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40552] New: r200 crashes in glclear when running the wine d3d tests.
Date: Thu,  1 Sep 2011 08:11:54 -0700 (PDT)	[thread overview]
Message-ID: <bug-40552-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r200 crashes in glclear when running the wine d3d
                    tests.
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r200
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: stefandoesinger@gmx.at


Created an attachment (id=50813)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=50813)
last log lines, assertion and backtrace.

When running the Wine(www.winehq.org) ddraw/d3d unit tests with r200 they crash
due to a failing assertion. The clear is done on a texture attached to a
framebuffer. It looks like Mesa is falling back to software, the SW renderer is
trying to map the texture into memory and this triggers the assertion.

I have not been able to reproduce this in a stand-alone application yet. I'll
attach a backtrace and the failing assertion. I'll also file a bug report for
the fact that r200 falls back to software at all, I think the hardware could do
this clear just fine.

-- 
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-09-01 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 15:11 bugzilla-daemon [this message]
2012-12-03  0:30 ` [Bug 40552] r200 crashes in glclear when running the wine d3d tests 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-40552-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.