using the 20100210.f0d760bf version of xorg. i get random crashes. also tracked on https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/525032 see there for some attached files including lspci dmesg etc. uploading the XorgLogOld file here however. not sure how to diagnose this, will be happy to test in whatever way you guys suggest.
Created attachment 33468 [details] XorgLogOld
RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu10 libgl1-mesa-glx 7.8.0~git20100210.f88b43e8-0ubuntu0sarvatt~karmic libdrm2 2.4.18+git20100217.2d9990c7-0ubuntu0sarvatt~karmic xserver-xorg-video-intel 2:2.10.0+git20100210.f0d760bf-0ubuntu0sarvatt2~karmic xserver-xorg-video-ati 1:6.12.99+git20100218.a3b730ec-0ubuntu0sarvatt~karmic SourcePackage: xorg Uname: Linux 2.6.31-19-generic x86_64 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 09/03/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: NT94510J.86A.4092.2007.0903.0307 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GNT dmi.board.vendor: Intel Corporation dmi.board.version: AAC96320-401 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrNT94510J.86A.4092.2007.0903.0307:bd09/03/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GNT:rvrAAC96320-401:cvn:ct2:cvr: fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-19-generic
commit c715089f49844260f1eeae8e3b55af9468ba1325 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Sep 23 00:43:56 2009 +0100 drm/i915: Handle ERESTARTSYS during page fault During a page fault and rebinding the buffer there exists a window for a signal to arrive during the i915_wait_request() and trigger a ERESTARTSYS. This used to be handled by returning SIGBUS and thereby killing the application. Try 'cairo-perf-trace & cairo-test-suite' and watch X go boom! The solution as suggested by H. Peter Anvin is to simply return NOPAGE and leave the higher layers to spot we did not fill the page and resubmit the page fault.
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.