All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27521] New: corrupted rendering with vbo + kms + rv515 (hits Blender 2.50!)
Date: Wed,  7 Apr 2010 12:04:35 -0700 (PDT)	[thread overview]
Message-ID: <bug-27521-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: corrupted rendering with vbo + kms + rv515 (hits
                    Blender 2.50!)
           Product: Mesa
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/Radeon
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: wixorpeek@gmail.com


Created an attachment (id=34773)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=34773)
program triggering the bug (compile with -std=c99)

Environment:
  - Debian Linux, vanilla kernel 2.6.33,
  - mesa 7.7.1-1,
  - radeon ddx 1:6.12.192-2 (changelog says: pull from upstream master up to
commit 5c256808)
  - libdrm 2.4.18-3
  - Radeon x1300 (xorg says: 1002:7142:1043:0162 ATI Technologies Inc RV515 PRO
[Radeon X1300/X1550 Series] rev 0, ...)

When using Blender's 2.50 VBO rendering mode, some mesh faces are not drawn.
The rendering is otherwise clean and correct. This occurs iff both VBO and KMS
are enabled.

Using BuGLe (http://www.opengl.org/sdk/tools/BuGLe) i have obtained trace of
opengl calls made by Blender (attached) and created a minimal program need to
reproduce the bug. It should render rotating gray cube with slight orange
silhouette. Program's source is attached, see comments there for details.

AFAIR the bug was already sitting there when I first tried KMS, which was
around October 18.

In the other news, if VBO is large, I get this on the console:
*********************************WARN_ONCE*********************************
File r300_draw.c function r300TryDrawPrims line 671
Rendering was 7 commands larger than predicted size. We might overflow  command
buffer.
***************************************************************************
This does not depend on KMS being enabled or not. 242406 indices and 40803
vertices are sufficient to reproduce this, but it's not strict lower bound.

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

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

             reply	other threads:[~2010-04-07 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 19:04 bugzilla-daemon [this message]
2010-04-07 19:05 ` [Bug 27521] corrupted rendering with vbo + kms + rv515 (hits Blender 2.50!) bugzilla-daemon
2010-04-08  8:12 ` bugzilla-daemon
2010-04-09 12:08 ` bugzilla-daemon
2010-04-09 19:29 ` bugzilla-daemon
2010-04-10  5:41 ` 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-27521-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.