[Bug 27571] New: Regression: r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer.

* [Bug 27571] New: Regression: r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer.
@ 2010-04-10  4:57 bugzilla-daemon
  2010-04-10  4:58 ` [Bug 27571] " bugzilla-daemon
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: bugzilla-daemon @ 2010-04-10  4:57 UTC (permalink / raw)
  To: dri-devel

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
--

^ permalink raw reply	[flat|nested] 5+ messages in thread