Assume this issue was resolved via kernel upgrade. *** This bug has been marked as a duplicate of bug 864430 ***