Oh yes, my bad, it wasn't a duplicate. However I think that most of the
respondents probably suffered from this bug and not the one you
described. If you think your bug still needs to be fixed on 2.6.32 feel
free to unmark it as a duplicate.
It's very interesting that you don't have the problem wi
Kernel developers are looking into it and may need some testing or feedback:
https://bugzilla.kernel.org/show_bug.cgi?id=30342
I can't do testing myself as the computer on which I encountered the bug
was not mine.
** Bug watch added: Linux Kernel Bug Tracker #30342
http://bugzilla.kernel.org/s
*** This bug is a duplicate of bug 568090 ***
https://bugs.launchpad.net/bugs/568090
** This bug has been marked a duplicate of bug 568090
ath5k should be loaded with nohwcrypt parameter
* You can subscribe to bug 568090 by following this link:
https://bugs.launchpad.net/ubuntu/+source/li
What exactly is holding this bug back?
The bug is 1 year old, has a low-impact temporary fix, has been
reproduced many times (including duplicates like bug 565892), and makes
wifi almost entirely unusable to anyone unaware of the workaround.
--
You received this bug notification because you are
I still have the same problem on a fully updated Maverick (installed
from scratch from the 10.10 CD).
Before learning about this nohwcrypt workaround I did a bit of investigation
and found the following: The cause of the high and unpredictable latencies is
that packets are dropped depending on t