Thanks for the links. From what we're seeing, it doesn't look like the same failure, though another bug reported by someone here looks like it may be what they're seeing. (They're seeing actualy watchdog resets.)

The issue we're seeing is the driver going into a spin because it can't reset the OMAP/GL into a sane state that it recognizes. And rather than eventually giving up, it continually tries to reset the chip... eating CPU and battery as it goes.

The real solution is to fix the driver's behavior. But until then, if something can prevent this behavior, using the settings to patch the run-time enough so the buffer is less likely to overflow may be a viable solution. (Since that seems to be a pre-cursor to this behavior.)