Bug 9338

Summary: i915_emit_param4fv: out of constants
Product: Mesa Reporter: Mirco Müller <macslow>
Component: Drivers/DRI/i915Assignee: Ian Romanick <idr>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: medium CC: wade
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Mirco Müller 2006-12-13 20:18:57 UTC 
How to reproduce this bug.

1.) Grab http://macslow.thepimp.net/cairo-dock.tar.bz2

2.) unpack, compile (needs gtk+ 2.x, cairo 1.2, glitz 0.5.6), run it with the
command ./cairo-dock (on an intel 915GM running on Xorg 7.1.1, Fedora Core 6) 

4.) This error-message is printed to stdout 71 times...

    i915_emit_param4fv: out of constants

before cairo-dock crashes with a seg-fault.

5.) This does not happen on nvidia-hardware using the closed source driver.

6.) It should run and look like this...

http://www.gnome-dock.org/trac/attachment/wiki/WikiStart/cairo-dock-ss.png?format=raw

on a composited desktop.
Comment 1 Eric Anholt 2011-07-13 10:17:10 UTC 
So, wow.  This is old.  I'm going to tentatively mark it FIXED because:

commit 61b512c47c9888f3ff117faf3aceccfb52d59c3a
Author: Eric Anholt <eric@anholt.net>
Date:   Wed Jul 29 23:37:04 2009 -0700

    i915: Update and translate the fragment program along with state updates.
    
    Previously, we were doing it in the midst of the pipeline run, which gave
    an opportunity to enable/disable fallbacks, which is certainly the wrong
    time to be doing so.  This manifested itself in a NULL dereference for PutRo
    after transitioning out of a fallback during a run_pipeline in glean glsl1.

Now, the program may still fail to get to hardware rendering because of exceeding the constant limits.  In the intervening years since this report was filed we also got better at packing constants, but that's no guarantee.  However, also in the intervening years, glitz is dead now so I can't really imagine going back and testing it...

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.