--Architecture(ia32,ia32e): ia32 & ia32e --Xf86_video_intel modesetting(5a793b0dcf2d5de408b55073858fcfba6d99f994) --Mesa: CVS tip --OS: FC5 --Xserver: randr-1.2-for-server-1.2(f05dd384d38c76dd9662933a03625dfef5b1c81f) using a wide-screen monitor, the 3D app such as glxinfo and glxgears failed with following error: bufmgr_fake.c:745: bmGenBufferStatic: Assertion `0' failed.
Created attachment 8356 [details] xorg.log
Created attachment 8357 [details] xorg.conf
The proplem is Mesa/i965 supposes the memories allocated for front/depth/back buffer in 2D driver are 4k aligned. But with the latest 2D driver applied, they are no longer 4k aligned. Option "Virtual 2048 2048" in xorg.conf (display section) can make them work fine.
Should be fixed in upstream Mesa now.
with mesa git branch master(af1d1e08e40c8c70dfa81e39724be11da94f938d) and Xserver git branch server-1.2-branch(8798c8cfa888521cc47173bf6db00b5724da4a54), the bug still exists.
Created attachment 8594 [details] xorg.conf
Created attachment 8595 [details] xorg.log
with the latest mesa branch(8518ddda7b5f8e43de4859042fe59f55aa0c2760) and Xserver (4e6872fca75b77c342a7e1e715b1c30dc2642a73) , the 3D app runs well on wide screen and error disappears.
According to my latest discovery, the problem still exists : last time when I verify the bug, I did as follows: 1. update the driver to the 965 machine (the machine connect to the monitor via a KVM) 2. start X and a 3D App on it from remote console(what is important, the KVM does not display the current screen at thar very moment) 3. switch the KVM to the 965 machine, and the 3D App run well. 4. close and start the App again within the same screen, no problem occurs. from above finding, I verify the bug. however, if the first time start X and then run a 3D App with the KVM displaying the same screen or just connect the machine with monitor(using no KVM), the App will fails with the original error info: bufmgr_fake.c:745: bmGenBufferStatic: Assertion `0' failed. after the error occur, in order to be successful, X has to be killed and start after switch KVM to another screen. In conclusion, the error occurs when starting X with KVM indicate to the same screen, otherwise, it's OK.
The above comment may be kind of confusing and misleading by the role of KVM, however, the key issue is that directly connecting monitor to the machine still have the bug when starting a 3D App.
Previous testing wasn't quite thorough enough and I hit sizes with page-aligned pitch * height anyway. Fixed in modesetting for a root window size of 1680x1050 now.
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.