The reverse bisect reported commit 9fc377799bc9bfd8d5cb35d0d1ea2e2458cbdbb3 as the fix for this bug. However, that does not make sense. That commit is a merge of scsi-misc.
We may have reported a commit as bad when it was actually good during the bisect process. Maybe we just didn't test for long enough. The easiest solution might be to use either the quantal or raring backport kernel if you plan on running Precise. Is that something you would consider? If so, it would be good to test the backport kernel for several days to ensure it really fixes the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984265 Title: Keyboard becomes all but unusable after Precise runs for so long To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/984265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
