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
@Alex
sounds more like a atheros driver issue. are you on intrepid? If so,
please try the latest daily liveCDs of jaunty development release.
** Changed in: linux (Ubuntu)
Sourcepackagename: network-manager => linux
--
Critical system slowdown; buffer i/o errors and ata7 errors
https://bugs.launchpad.
I suppose the next step is to try a failed connection from the cli,
without logging in to X. Meh, and maybe I will wait for the beta
release to do further testing.
--
Critical system slowdown; buffer i/o errors and ata7 errors
https://bugs.launchpad.net/bugs/338470
You received this bug notifica
confirming that this only happens on jaunty, not intrepid. Also,
removing an unnecessary step to produce.
** Summary changed:
- Critical system slowdown; buffer i/o errors
+ Critical system slowdown; buffer i/o errors and ata7 errors
** Description changed:
Ok, here is how I have produced th