On Thu, 2009-04-16 at 11:12 +0200, Johannes Berg wrote: > > I have been thinking two ways to fix this, either disabling the timer > > for the duration of the scan or add a check for scan scan in > > ieee80211_associated(). I started implementing the former but haven't > > finished it yet. It would be great if someone else can fix it. > > But that doesn't make sense to me now. ieee80211_associated() is only > run from the station work (ieee80211_sta_work) which doesn't do anything > when we're scanning (and gets restarted on scan end). So even if last_rx > or last_beacon isn't updated we should only run the evaluation of that > after the scan finishes. > > I'll try to reproduce this. Can't. Scanning here, with 4965, takes almost 7 seconds, but all I see is, _after_ the scan, a probe: [ 1534.592164] wlan0: beacon loss from AP 00:1d:7e:4a:a1:ab - sending probe request In a noisy environment I guess that probe or the reply could get lost, but that seems unlikely to happen _every_ time. Marcel, you will have to provide more information -- like kernel logs for example, and maybe packet captures. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
