I do think its an ath9k driver issue. I managed to have top running the last test, when I was testing out the cli. (Unfortunately, I could not figure out the syntax for iwconfig. I thought all I needed was a key "the_key" directive, but errored out)
top showed ath9k taking up all the cpu @Alexander - This works fine on intrepid. This is a jaunty only issue. Should I just invalidate this bug report, and file a comment on the master atheros bug report? I suppose not, but I could leave a comment anyway. I'll try to pay attention to this changelog, and retest whenver there is mentionnn of ath9k: http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_2.6.28-8.28/changelog ** Summary changed: - Critical system slowdown; buffer i/o errors and ata7 errors + [jaunty] [ath9k] Critical system slowdown; buffer i/o errors and ata7 errors ** Tags added: ath9k ** Tags removed: regression ** Summary changed: - [jaunty] [ath9k] Critical system slowdown; buffer i/o errors and ata7 errors + [jaunty] [ath9k] Critical system slowdown; buffer i/o errors and ata7 errors on failed encryted connection attempt -- [jaunty] [ath9k] Critical system slowdown; buffer i/o errors and ata7 errors on failed encryted connection attempt https://bugs.launchpad.net/bugs/338470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
