All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27571] New: Regression: r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer.
Date: Fri,  9 Apr 2010 21:57:24 -0700 (PDT)	[thread overview]
Message-ID: <bug-27571-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Regression: r600 CS checker rejects GL_DEPTH_TEST w/o
                    depth buffer.
           Product: DRI
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: nbowler@draconx.ca


Created an attachment (id=34858)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=34858)
Test case.

The command stream checker recently added to the radeon driver kills
programs which render to a target which does not have a depth buffer
whilst GL_DEPTH_TEST is enabled.  Instead of simply not performing
depth buffer operations, the result is program termination and some
rather cryptic error messages:

  drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command
  stream.  See dmesg for more info.

and in dmesg:
  radeon 0000:03:00.0: z/stencil with no depth buffer
  radeon 0000:03:00.0: r600_packet3_check:1109 invalid cmd stream 815
  [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

I first noticed this when a program that works using 2.6.33 died
rendering to a FBO, but it is trivially reproducible without using
anything fancy.  A test case is attached which works normally with
either Linux 2.6.33, the software rasterizer, or the intel driver.
The failure is reproducible with both mesa 7.8.1 and git master.

-- 
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-10  4:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10  4:57 bugzilla-daemon [this message]
2010-04-10  4:58 ` [Bug 27571] Regression: r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer bugzilla-daemon
2010-04-12  0:00 ` bugzilla-daemon
2010-04-13  1:54 ` bugzilla-daemon
2010-04-23 10:15 ` 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-27571-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.