On Wed, Aug 10, 2011 at 3:38 AM, Robert Högberg <robert.hogb...@gmail.com> wrote: > Hi, > > I know NetworkManager scans the network every two minutes. I've had > problems with this and disabled it by explicitly setting a BSSID so > this is not a problem anymore. > > I have verified that my problem is related to the noise floor > calibrations by modifying the ATH_LONG_CALINTERVAL constant within the > ath9k driver. My network freezes each time that calibration timer is > triggered. And, if I completely disable the calibrations I have no > problems at all.
there is a option to disable ani in ath9k via debugfs (/sys/kernel/debug/ieee80211/phy/ath9k/disable_ani) please echo 1 to it and test. > > I've seen the problem on both Ubuntu 11.04 and Fedora 15, but Windows > 7 and FreeBSD seem to work well. > > Thanks for keeping an eye on this problem Adrian. It was my intention > to get back to the ath9k devel list when I had done some more testing > on FreeBSD, but I've had some problems getting FreeBSD up and running > properly and I've been short on time. > > When installing FreeBSD the computer locks up when it tries to connect > to my AP. I believe this may be caused by WPA because when I first > tried FreeBSD using the live CD I disabled the encryption to simplify > my testing and then all worked well. But, I would like to do some more > tests before I can tell what seems to cause the crashes. > > Adrian, can you verify that also the FreeBSD driver performs > calibrations every 30 seconds? > > I'll try to get my FreeBSD installation up and running and see if I > can get some debug information from there. Is there's something > particularly interesting I should try in FreeBSD? Can I get some kind > of debug data without recompiling the kernel/ath module? Can I get a > backtrace or similar information from a crashed system? > > Robert > > > 2011/8/9 Galen <gal...@zinkconsulting.com>: >> I haven't reviewed the full thread here - but have you made 100% sure that >> there is not some kind of WiFi connection manager running in the background >> on the Linux system? Just something to double check... those connection >> managers frequently probe and cause network stalls, particularly at >> specific, likely human-programmed intervals (e.g. 30 seconds) like you're >> describing... >> >> Sure, it's stupidly simple, but Linux distros have deeply embedded WiFi >> connection managers and people sometimes miss them... >> >> -Galen >> >> On Aug 8, 2011, at 6:13 PM, Adrian Chadd wrote: >> >>> .. sorry, he isn't having issues with the AR5416 on FreeBSD but is under >>> ath9k. >>> >>> (Wow, is this the second time FreeBSD works where ath9k doesn't? I may >>> have to throw a little private party :-) >>> >>> Would someone like to take up the challenge? I'll help you wade >>> through the HAL if you'd like. >>> >>> >>> Adrian >>> >>> On 9 August 2011 09:12, Adrian Chadd <adr...@freebsd.org> wrote: >>>> Hi all, >>>> >>>> I'm just forwarding what Robert said. FreeBSD doesn't have the same >>>> interruptions as ath9k does on the AR5416. >>>> >>>> I don't have the time to go digging myself just now. >>>> >>>> On 3 August 2011 05:37, Robert Högberg <robert.hogb...@gmail.com> wrote: >>>>> An update to previous mail.. >>>>> >>>>> I tried the i386 version of FreeBSD 9.0 beta (instead of amd64) and >>>>> that one worked much, much better. No network interruptions every 30 >>>>> seconds in FreeBSD 9.0 beta 1, but I only ran the test for a few >>>>> minutes. Would you expect the noise floor calibrations to happen every >>>>> 30 seconds in FreeBSD also or is the interval different there? >>>>> >>>>> I'll continue investigating. >>>>> >>>>> (You may want to look into why the ath driver doesn't work on amd64..) >>>>> >>>>> Robert >>>>> >>>>> 2011/8/2 Robert Högberg <robert.hogb...@gmail.com>: >>>>>> I tried FreeBSD and the computer crashed when I tried to enable the WLAN. >>>>>> >>>>>> I'm no FreeBSD user so I'm not sure I got things right, but here's what >>>>>> I did: >>>>>> * Boot FreeBSD from USB stick (WLAN device was detected correctly and >>>>>> ath0 created) >>>>>> * ifconfig wlan0 create wlandev ath0 >>>>>> * ifconfig wlan0 up (This caused the computer to freeze. No output, >>>>>> and no input possible. I waited minutes but nothing happened.) >>>>>> >>>>>> I attach dmesg output after boot. >>>>>> >>>>>> /Robert >>>>>> >>>>>> 2011/8/2 Adrian Chadd <adr...@freebsd.org>: >>>>>>> Ah, that it works well in Windows is a good sign. >>>>>>> >>>>>>> Would you mind doing me a favour? Could you spin up FreeBSD-9.0-BETA1 >>>>>>> on a temporary disk (eg a USB thumb drive) and see if it exhibits the >>>>>>> same behaviour? >>>>>>> >>>>>>> >>>>>>> Adrian >>>>>>> >>>>>>> On 2 August 2011 04:19, Robert Högberg <robert.hogb...@gmail.com> wrote: >>>>>>>> 2011/7/30 Adrian Chadd <adr...@freebsd.org>: >>>>>>>>> Have you tried another ath9k NIC? Another AR5416 NIC? >>>>>>>> >>>>>>>> I've tried an AR9271 NIC (USB ID 0cf3:9271) and it works very well. I >>>>>>>> only have one AR5416 NIC to test I'm afraid. >>>>>>>> >>>>>>>> >>>>>>>>> Is it possible this NIC is slightly weirdly damaged? >>>>>>>> >>>>>>>> Maybe, but the card works well with the Windows 7 drivers. But I guess >>>>>>>> it's possible that the noise floor calibration functionality is >>>>>>>> broken/problematic on this card and the Windows driver knows this and >>>>>>>> avoids or adapts to the problem. After all, I don't see any problems >>>>>>>> with the calibration disabled so maybe the Windows driver doesn't use >>>>>>>> the calibration either. But I don't know.. >>>>>>>> >>>>>>>> TP-Link has released a v2 version of this TL-WN851N NIC (I'm using v1) >>>>>>>> which suggests the first version may not have been perfect. Maybe v1 >>>>>>>> was "weirdly damaged" and they fixed it in the second version. I don't >>>>>>>> know what the differences are between the two versions, but I think >>>>>>>> they used AR5416 in both versions. >>>>>>>> >>>>>>>> Robert >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> _______________________________________________ >>> ath9k-devel mailing list >>> ath9k-devel@lists.ath9k.org >>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >> >> > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel > -- shafi _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
