Not that anyone was interested... but it *seems* that this problem is resolved as of kernel 2.6.31-13. I'll post again if that turns out not to be the case with further testing.
Not that anyone was interested... but it *seems* that this problem is resolved as of kernel 2.6.31-13. I'll post again if that turns out not to be the case with further testing.