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 54832] New: Regression: 185ed2105829d6f5eb19edb9abbf0d7977e157c3 breaks swtcl on r300g
Date: Thu, 13 Sep 2012 02:27:19 +0000	[thread overview]
Message-ID: <bug-54832-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 54832
           Summary: Regression: 185ed2105829d6f5eb19edb9abbf0d7977e157c3
                    breaks swtcl on r300g
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: tstellar@gmail.com
                CC: brianp@vmware.com


Lightsmark stopped working on my r300 laptop with swtcl following this commit:

commit 185ed2105829d6f5eb19edb9abbf0d7977e157c3
Author: Brian Paul <brianp@vmware.com>
Date:   Fri May 25 09:44:53 2012 -0600

    draw: simplify index buffer specification

    Replace draw_set_index_buffer() and draw_set_mapped_index_buffer() with
    draw_set_indexes() which simply takes a pointer and an index size.


When I start Lightsmark, it crashes during the "loading..." screen after a few
seconds, before the demo starts rendering the scene.  Prior to the crash, the
debug statement ("warning index out of range") @ draw_pt_vsplit_tmp.h:59 is
printed several times, followed by the message:

draw_pipeline_run: max_index (7589) outside vertex buffer (300)

and then a segfault.

-- 
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:[~2012-09-13  2:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13  2:27 bugzilla-daemon [this message]
2012-09-13 13:05 ` [Bug 54832] Regression: 185ed2105829d6f5eb19edb9abbf0d7977e157c3 breaks swtcl on r300g bugzilla-daemon
2012-09-13 13:26 ` bugzilla-daemon
2012-09-13 14:21 ` bugzilla-daemon
2012-09-17  0:35 ` [Bug 54832] Piglit Regression: r300g swtcl 185ed21 draw: simplify index buffer specification bugzilla-daemon
2012-09-17  0:43 ` bugzilla-daemon
2012-09-17  0:46 ` bugzilla-daemon
2012-09-17  1:37 ` bugzilla-daemon
2012-09-17  2:13 ` bugzilla-daemon
2012-09-22 14:34 ` 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-54832-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