From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 26962] New: fbo/fbo-nodepth-test: Invalid command stream Date: Mon, 8 Mar 2010 09:24:00 -0800 (PST) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.sourceforge.net To: dri-devel@lists.sourceforge.net List-Id: dri-devel@lists.freedesktop.org http://bugs.freedesktop.org/show_bug.cgi?id=26962 Summary: fbo/fbo-nodepth-test: Invalid command stream Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: edwintorok@gmail.com Created an attachment (id=33865) --> (http://bugs.freedesktop.org/attachment.cgi?id=33865) Xorg.0.log, dmesg, and glxinfo Running fbo/fbo-nodepth-test from piglit fails: drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info. dmesg: [30757.053682] radeon 0000:01:00.0: z/stencil with no depth buffer [30757.053687] radeon 0000:01:00.0: r600_packet3_check:1055 invalid cmd stream 793 [30757.053689] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! Mesa 7.8 branch, tested commits ba8f4c5d36e6c9cd806a4c3360a8202b1f81ee05, and df9bf78f888702542a506f551204a2e7dc8b7df1, they both show this problem. Kernel is based on glisse's drm-radeon-next (2.6.33) tree, commit 0d95f1a47d7e927e70a8748f6e54c911acf531d1. Linux debian 2.6.33-00174-g0d95f1a #1 SMP PREEMPT Sun Mar 7 20:29:30 EET 2010 x86_64 GNU/Linux For Xorg/dmesg/glxinfo logs see the attachment. The DDX is 6.12.191. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ Download Intel® 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 --