This issue seems to have been resolved in kernels newer than 2.6.33-500-omap-5. We haven't seen it in 2.6.33-502 nor in Maverick.
This issue seems to have been resolved in kernels newer than 2.6.33-500-omap-5. We haven't seen it in 2.6.33-502 nor in Maverick.