Comment 9 for bug 375545

I can't find anything in those logs that tells me what is going on. I think we should report this upstream. To make sure it is not something they have fixed already, you should test a newer driver. If it is still there, we report it upstream with the logs from the newer drivers. You have two options:
1. You can test the 2.7.1 driver from the x-updates PPA (Personal Package Archive) at https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/ . This PPA contains updated stable drivers that were released too late to get into jaunty. These packages solve a number of problems, but has a small chance of introducing new ones.
2. You can test the latest driver from the GIT master respository. This is the development version of the driver, and you can get it from the xorg-edgers PPA at https://launchpad.net/~xorg-edgers/+archive/ppa (see also info on https://launchpad.net/~xorg-edgers). This has a much higher chance of breaking something, is maybe a bit more complicated, but will probably make the intel developers a little more happy.

If you can test one of these and upload the Xorg.0.log if it does not fix things, then I can file the bug report upstream. I will then ask you to subscribe to it too in case the intel devs have questions or possible workarounds. You may also file the bug upstream yourself if you want to give it a try. There are instructions at http://intellinuxgraphics.org/how_to_report_bug.html. If you file it yourself, I will subscribe to the upstream bug and be able to help you with any questions.