Bug 8771

Summary: [i965] Doom3-demo abort with an Assertion failed
Product: Mesa Reporter: veelion (inactive account) <weiliang.chong>
Component: Drivers/DRI/i965Assignee: Zou Nan hai <nanhai.zou>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: high CC: gordon.jin, mesa-dev
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Xorg.log
xorg.conf
patch to fix it

Description veelion (inactive account) 2006-10-25 22:54:45 UTC
both on G965(64-bit OS) and Q965(32-bit OS), run Doom3 demo to the main menu, 
and then select an "new game", in several seconds after "loading" 100%, Doo3-
demo abort. on the console, the information is,
-------------------------------------------
	doom.x86: intel_regions.c:231: intel_region_data: Assertion `dst_offset + 
dstx + width + (dsty + height - 1) * dst->pitch * dst->cpp <= dst->pitch * dst-
>cpp * dst->height' failed.
	signal caught: Aborted
	si_code -6
	Trying to exit gracefully..
	--------- Game Map Shutdown ----------
	--------------------------------------
	idRenderSystem::Shutdown()
	tried to free block on referenced list
	doom.x86: bufmgr_fake.c:217: free_block: Assertion `0' failed.
	double fault Aborted, bailing out
	shutdown terminal support
---------------------------------------------
Comment 1 veelion (inactive account) 2006-10-26 00:06:27 UTC
Created attachment 7524 [details]
Xorg.log
Comment 2 veelion (inactive account) 2006-10-26 00:06:47 UTC
Created attachment 7525 [details]
xorg.conf
Comment 3 Zou Nan hai 2006-11-23 17:50:32 UTC
Created attachment 7886 [details] [review]
patch to fix it

if the texture width is too small,
the span right in the mipmap layout calculation 
will calculate out of range.
so disable the span right in level 1 mipmap
Comment 4 Gordon Jin 2007-01-04 22:32:47 UTC
This problem goes away with the current upstream code, so I'm closing.
Comment 5 Adam Jackson 2009-08-24 12:24:47 UTC
Mass version move, cvs -> git

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.