Bug 13454

Summary: [855gm]glxgears can not run
Product: Mesa Reporter: Pi, Fengming <fengming.pi>
Component: Drivers/DRI/i915Assignee: Default DRI bug account <dri-devel>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: medium CC: zhenyu.z.wang
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: xorg log file
Possible fix

Description Pi, Fengming 2007-11-30 00:25:44 UTC
System Environment:
--------------------------

--Platform: 855GM
--Architecture: ia32
--2D driver: git commit:75ef3e669dac1259d282dcc8f54b197fc19f22b3
--3D driver: Mesa master commit:dc88a96631c21c2bc2cdffefc8947e8924d77c91
--DRM:   git commit:309b2c4c05d02a7e7311a9491b74044f6c7f06a4
--Xserver: git commit:8a079be0dd0f2ce37868988cde4ac8895522b088
--Kernel: 2.6.22

Description:
Using the latest git code on 855gm,glxgears can not run,following error you display:
glxgears: intel_tris.c:114: intelStartInlinePrimitive: Assertion `intel->batch->id == intel->last_state_batch_id' failed.
Aborted
 
Reproduce steps:
1 X &
2 glxgears
Comment 1 Pi, Fengming 2007-11-30 00:42:44 UTC
Created attachment 12862 [details]
xorg log file
Comment 2 Michel Dänzer 2007-11-30 01:48:27 UTC
Created attachment 12863 [details] [review]
Possible fix

Does this patch fix it?
Comment 3 Pi, Fengming 2007-12-02 18:21:28 UTC
Applied to Comment #2
Good job! glxgears can run on 855gm with your patch.
Comment 4 Jesse Barnes 2007-12-02 19:37:15 UTC
Fengming or Michel, is the patch committed?  If not, we should probably leave the bug open to remind us until it is...
Comment 5 Pi, Fengming 2007-12-02 20:47:35 UTC
Applied to Comment #4

Ok,we will leave the bug open until the patch commit
Comment 6 Michel Dänzer 2007-12-03 00:39:14 UTC
Fix pushed.
Comment 7 Pi, Fengming 2007-12-04 01:11:30 UTC
ok,I pull the latest git code today and using it on my 855gm,the bug doesn't happen.

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.