Uh oh. Are inetl's drivers not up to par again??
http://www.phoronix.com/scan.php?pag...y_breaks&num=2
[edit]
oh this is not good it may not even be just drivers. i'm surprised this story passed under the radar.
[edit2]In talking over this situation with Keith Packard, who heads the Intel OSTC developers working on the Linux graphics code, the culprit for most of these issues may be within the Intel's Linux power management code for Sandy Bridge, but he shared they seem to be facing a number of platform-specific issues this generation so it could be a more isolated problem as well. There's also likely at least a second separate issue coming into play too and that's with the Mesa driver where some OpenGL games (such as Padman and OpenArena) are crashing gracefully but independent problems from the rest.
Couple more quotes for context.
The next step in trying to get a Linux 2.6.38 Git kernel build to work and hopefully fix the Sandy Bridge issues was reverting back to the original Linux 2.6.35 kernel that ships with Ubuntu 10.10. But it turns out there too this problem can take place if you force the CPU load too high there with multiple threads, the system can also go down, but the problem just seems to be a lot easier to hit with the Linux 2.6.37 kernel.My next step was to verify this with one of the common OpenGL benchmarks. After a quick FORCE_TIMES_TO_RUN=1 phoronix-test-suite benchmark nexuiz had worked out with hardware acceleration, it appeared the situation was going easy again. With this Intel H67 + Intel Core i5 2500K system running Ubuntu 10.10 with the Linux 2.6.37 kernel, Mesa 7.11-devel, xf86-video-intel 2.14, and libdrm 2.4.23, I then decided to run the common OpenGL games such as those in the recent open-source ATI Mesa benchmarks. It's a simple, phoronix-test-suite batch-run vdrift nexuiz warsow openarena padman smokin-guns and selected 800 x 600, 1024 x 768, 1280 x 1024, and 1920 x 1080 as the resolutions for each test to see how well the Sandy Bridge graphics and driver were scaling. However, in the end, I did not have a single valid result for one reason or another with each test.
VDrift ran the best overall, did not crash once even when testing it at all of the resolutions, and provided decent frame-rates, but there were random artifacts appearing on the screen. But this was just the start of the problems
Bookmarks