[Bug 341952] Re: ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout"
Giovanni Bajo
giovannibajo at gmail.com
Sat May 2 11:11:10 UTC 2009
I noticed that, immediately after booting the computer, ath_pci
(madwifi) works correctly, but then it starts degrading in performance
(both latency and bandwidth) and in a few minutes it's back to a
horrible state like this:
--- 192.168.1.1 ping statistics ---
18 packets transmitted, 18 received, 0% packet loss, time 17026ms
rtt min/avg/max/mdev = 2.530/5.401/12.738/2.476 ms
(notice: this is the gateway and it's always been stable < 1ms in ubuntu
hardy usually). Speed tests go from an optimum 6/1 Mbit (which is my
nominal speed) to 1/0.128.
$ lsmod | grep ath
ath_rate_sample 21888 1
ath_pci 224832 0
wlan 259232 5 wlan_tkip,wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 339088 3 ath_rate_sample,ath_pci
multipath 16512 0
I'm using this snapshot: madwifi-hal-0.10.5.6-r4016-20090429.
Can somebody please certify which exact driver was being used by Ubuntu
Hardy? Was it MadWifi? If so, which exact version/snapshot? I would like
to test with that exact driver. Otherwise, I'll have to assume that
running "ath5" once on my card misconfigured it in a way that madwifi is
not able to recover anymore.
--
ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout"
https://bugs.launchpad.net/bugs/341952
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.
More information about the kernel-bugs
mailing list