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 43096] New: r300g: r300_emit_draw_elements() refusing to render when max_index = 0xffffffff
Date: Sat, 19 Nov 2011 21:26:32 +0000	[thread overview]
Message-ID: <bug-43096-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 43096
           Summary: r300g: r300_emit_draw_elements() refusing to render
                    when max_index = 0xffffffff
    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


Created attachment 53692
  --> https://bugs.freedesktop.org/attachment.cgi?id=53692
Callstack from error message

I'm not exactly sure if this is a bug in r300g or st/mesa, but none of the
leader portraits are rendered in Civ4 and this error message is being printed:

r300: Got a huge number of vertices: 310, refusing to render (max_index: -1).

The reason this error message is being printed is because max_index is
0xffffffff, so this if statement at r300_render.c:448 evaluates to true:

if (count >= (1 << 24) || max_index >= (1 << 24)) {
        fprintf(stderr, "r300: Got a huge number of vertices: %i, "
                "refusing to render (max_index: %i).\n", count, max_index);
        return;
}

I'm not sure if the state tracker is wrong for passing 0xffffffff as the
max_index or if the driver needs to handle a max_index of 0xffffffff as a
special case, because it is the default value for pipe_draw_info->max_index.  I
have captured the call stack when this error message is printed and attached it
to this bug report.

-- 
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-11-19 21:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19 21:26 bugzilla-daemon [this message]
2011-11-19 21:28 ` [Bug 43096] r300g: r300_emit_draw_elements() refusing to render when max_index = 0xffffffff bugzilla-daemon
2011-11-20  4:22 ` bugzilla-daemon
2011-11-20  4:48 ` bugzilla-daemon
2011-11-20 15:35 ` bugzilla-daemon
2011-11-20 16:11 ` bugzilla-daemon
2011-11-20 17:33 ` bugzilla-daemon
2011-11-20 17:54 ` bugzilla-daemon
2011-11-20 21:16 ` 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-43096-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