Hi, That's interesting. I have found the AR9280 to do the same. I hadn't gone digging into it though, I've been busy with other things but it was on my todo list. So thankyou for finding it. :-) Specifically (and this is all under BSD): * I'd start rx'ing radar errors; * then they'd become crc errors; * after some indeterminate amount of time, they'd drift back to being radar errors. I'll reproduce it on the AR9280 and let you know how it goes. Thanks for digging into it! Adrian ________________________________________ From: Zefir Kurtisi [zefir.kurtisi@xxxxxxxxxxx] Sent: Tuesday, 28 February 2012 3:57 AM To: Chadd, Adrian Cc: linville@xxxxxxxxxxxxx; ath9k-devel@xxxxxxxxxxxxxxx; linux-wireless@xxxxxxxxxxxxxxx; Rodriguez, Luis Subject: Re: [PATCH] ath9k: decouple RX error checking for DFS Hi Adrian, finally found an AR9280 and repeated the tests simultaneously, i.e. identical radar pulses go to AR9390 and AR9280. After several hours of continuous radar firing (pulse count in the 1M range), it looks like the AR9280 does not suffer from the reported problem, i.e. the PHY error is never reported in combination with other RX errors. The AR9390 OTOH always follows the following scheme: * it starts as expected with radar pulses being reported as PHY errors (RX descriptor word 11 set to status11=0x511) * after a short time (about 80% probability within 5-20 mins) a single CRC error is reported (status11=0x005) * the CRC error flag becomes sticky thereafter, all further radar pulses are reported with status11=0x515, i.e. PHY *and* CRC error The posted patch fixes this issue for monitor mode. Not sure about implications for the soon to follow master mode, though. On 02/27/2012 05:00 PM, Chadd, Adrian wrote: > Hi, > > Hm, so the AR9003 series NICs set PHY error _and_ decrypt/CRC error? On radar frames? > > Interesting! Have you checked to see if the AR9280 does the same? > > > > Adrian -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
