SUGGESTED FIX

http://sa.sfbay.sun.com/projects/java2d_data/6u10/6620073.0
                                     

EVALUATION

The same crash is reproducible on G35 board.
Unfortunately this means that we can't enable
the pipeline on any of the existing Intel boards.

We'll continue working with Intel on resolving these issues,
but at this point there's no other choice - leaving
the pipeline enabled is too much risk.
                                     

EVALUATION

Drivers on Intel 965G/GM (3000, X3000) chipset are known to be rather unreliable:
  http://news.zdnet.com/2100-9584_22-6184483.html
  http://softwarecommunity.intel.com/isn/Community/en-US/forums/2414/ShowForum.aspx

Apparently many native benchmarks (3DMark) can't finish on this board 
for the same reason.

The drivers on WinXP are told to be in even worse shape.

Also even though Intel had recently enabled hw TnL in the drivers the 
performance is pretty bad based on Firestarter and those imaging benchmarks
that can be ran before the driver dies.

So for now we will disable the pipeline on Intel G965, GM965.

(earlier Intel chipsets will also be disabled since they don't have hardware TnL)