Is this known to be separate issue from bug 349314? Perhaps folks here could try the test kernels in that bug and see if they resolve the problem.
Is this known to be separate issue from bug 349314? Perhaps folks here could try the test kernels in that bug and see if they resolve the problem.