System Environment: -------------------------- --Platform:945gm 915gm bearlake --Architecture(32-bit,64-bit,compatiblity): 32bit kernel: 2.6.23 drm commit 62df4f0a48776e55443d7f61a41e1ed0fb77b6ed mesa commit 544ab209e75ec3646d7edbafd736dcf4c93738cc xf86_video_intel commit 4fec18e07f2b23306e885d63c74661ae0e4b04d9 xserver commit 180a5aba4de3104fed8bc4e7d42a1e3a51575318 Bug detailed description: -------------------------- startx , run openarena , it soon hang system . Reproduce steps: ---------------- run openarena Current result: ---------------- hang system Expected result: ---------------- run normally
Created attachment 13714 [details] Xorg.0.log
Created attachment 13715 [details] backtrace
it seems following commit brings in this issue: commit a04b632350e5d0e9994fc667afc59407a39da0ba Author: Eric Anholt <eric@anholt.net> Date: Thu Jan 10 10:48:05 2008 -0800 [intel] Add more cliprect modes to cover other meanings for batch emits. The previous change gave us only two modes, one which looped over the batch per cliprect (3d drawing) and one that didn't (state updeast). However, we really want 4: - Batch doesn't care about cliprects (state updates) - Batch needs DRAWING_RECTANGLE looping per cliprect (3d drawing) - Batch needs to be executed just once (region fills, copies, etc.) - Batch already includes cliprect handling, and must be flushed by unlock ti (copybuffers, clears). All callers should now be fixed to use one of these states for any batchbuff emits. Thanks to Keith Whitwell for pointing out the failure.
it doesn't hang the system. it can be connected from other machine.
run with: ./glean -r test -t +fpexceptions can reproduce the same problem. but it will not freeze tty.
I failed to push some changes on Monday, need to grab them and test again on master.
I have tried latest git. the issue still exists. are the changes committed in?
*** Bug 14104 has been marked as a duplicate of this bug. ***
Pushed my patch today, which got OA working for me.
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.