On Thu, Jan 15, 2009 at 12:25:50PM -0800, Luis R. Rodriguez wrote: > On Thu, Jan 15, 2009 at 10:37:03AM -0800, Greg KH wrote: > > On Mon, Jan 05, 2009 at 09:04:32AM -0800, Luis R. Rodriguez wrote: > > > On Wed, Dec 31, 2008 at 11:52:32PM -0800, Joseph Cheek wrote: > > > > Hi all, > > > > > > > > Happy New Year! It's about 2:30 AM here and I'm up debugging my shiny > > > > new DWA-552 <AR5416+AR2133> XtremeN Desktop Adapter. Stock 2.6.28 gave > > > > me the dreaded "No ProbeResp from current AP" in syslog with a > > > > disconnect every few minutes, even after updating > > > > |IEEE80211_MONITORING_INTERVAL to (100 * HZ). It's highly annoying. > > > > > > This should be due to the fact that the RX filter disabled beaconing from > > > the current AP and mac80211 expects beacons from the AP. This was fixed > > > in wireless-testing but I do not see this pushed out for 2.6.28. > > > > > > Greg, this was fixed in Linus' tree via ffb826767bffda61426d964a8fc24a216a14b0bd, > > > merged by John on Fri, 21 Nov 2008, the patch is titled: > > > "ath9k: enable RXing of beacons on STA/IBSS". Just in case I've > > > provided the hunk below. Without this patch users will face this disconnect > > > issue on noisy environments where the beacons don't reach mac80211 within > > > a certain time frame dicated by mac80211. > > > > Thanks, I'll queue this up for 2.6.28, but it doesn't apply to > > 2.6.27-stable. If you want it there, can you please provide a backport > > for it? > > Thanks Greg -- it seems this was actually present in 2.6.27 since the > initial commit of ath9k. From the initial commit I see: > > --- on ath_calcrxfilter() > if (sc->sc_opmode == ATH9K_M_STA || sc->sc_opmode == ATH9K_M_IBSS || > sc->sc_scanning) > rfilt |= ATH9K_RX_FILTER_BEACON; > --- > > Seems we're good on 27 for this and this actually turned out to be a regression then. Thanks for confirming it, greg k-h -- 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
