Bug 38423

Summary: i965/gen5: fbo-maxsize fails on master
Product: Mesa Reporter: Chad Versace <chadversary>
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: Linux (All)   
See Also: https://bugs.freedesktop.org/show_bug.cgi?id=37871
Whiteboard:
i915 platform: i915 features:

Description Chad Versace 2011-06-17 15:11:56 UTC 
mesa: 10562fbc5c630b7f1a97344bc3d6b2649c7393a5
xf86-video-intel: a62db5b050dee10246c02c72385358acb5e72b56
piglit: f460f2541f812f60f5feb2a9a75cc32ed874a19c

fbo-maxsize fails sporadically. On each run, regardless if it fails or succeeds, it always emits this error message:
    i965: Single primitive emit potentially exceeded available aperture space
Comment 1 Chris Wilson 2011-06-19 09:48:08 UTC 
Chipset and dmesg for aperture size?
Comment 2 Chad Versace 2011-06-20 16:42:26 UTC 
chipset:  00:02.0 0300: 8086:0046 (rev 02)

Where do I find the aperture size? A `dmesg | grep -i aperture` returned nothing.

btw, anholt thought the problem may be that we're advertising too large of a GL_MAX_TEXTURE_SIZE.
Comment 3 Chris Wilson 2011-06-26 01:34:35 UTC 
That's what I thought it will be, hence the request for aperture size (which is in the dmesg and lspci). And its not the overreporting of MAX_TEXTURE_SIZE tbh, but the mishandling of it...

See also bug 37871.
Comment 4 Chad Versace 2011-07-26 12:55:56 UTC 
See also https://bugs.freedesktop.org/show_bug.cgi?id=37871
Comment 5 Kenneth Graunke 2014-08-16 21:13:35 UTC 
Works for me on Ironlake with Mesa master.

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.