On Mon, Dec 1, 2008 at 5:12 PM, Luis R. Rodriguez <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 1, 2008 at 2:03 PM, Albert Gall <[EMAIL PROTECTED]> wrote:
>>> Luis R. Rodriguez wrote:
>>>
>>> Then upgrade your compat-wireless.
>>
>> Upgraded to wireless-compat-2008-12-01 and the problem persists.
>>
>> /usr/local/src/compat-wireless-2008-12-01 {0}-{0} # dmesg
[snip]
>> [ 2500.030537] ath5k phy1: noise floor calibration timeout (2442MHz)
>> [ 2510.705001] ath5k phy1: noise floor calibration timeout (2442MHz)
>> [ 2522.030443] ath5k phy1: noise floor calibration timeout (2442MHz)
>> [ 2532.705002] ath5k phy1: noise floor calibration timeout (2442MHz)
>> [ 2544.030243] ath5k phy1: noise floor calibration timeout (2442MHz)
>> [ 2555.030558] ath5k phy1: noise floor calibration timeout (2442MHz)
>> [ 2565.705001] ath5k phy1: noise floor calibration timeout (2442MHz)
>> [ 2576.705001] ath5k phy1: noise floor calibration timeout (2442MHz)
>> /usr/local/src/compat-wireless-2008-12-01 {0}-{0} #
>
> What does 'modprobe -l ath5k' show? After how long does this pop up?
> Do you associate, and get an IP and eventually it happens? How long
> after?Felix's patch should make the timeouts not bork the hardware, but the code still can print this warning. Since it runs every 10s it's not surprising that there will be a cascade of them all 10s apart if the medium gets noisy. There are TODOs and FIXMEs all over this particular bit of code, it would be nice to address some of them. There's ANI still to be done, and IIRC the calibration procedure is a bit different between ath5k and the various HALs. -- Bob Copeland %% www.bobcopeland.com _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
