lkml.org 
[lkml]   [2009]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: ath9k becon loss messages
From
Date
Jaswinder Singh Rajput <jaswinder@kernel.org> writes:

>> And besides that, I think one can easily remotely trigger this
>> message and flood the logs. So it should probably _also_ be
>> ratelimited.
>
> normally it prints after 120 seconds:
>
> [ 1078.848434] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 1198.822913] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 1318.824931] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request

Then there is something happening in ath9k or your AP which prevents
ath9k from receiving beacons. Try pinging your AP with 100 ms
interval. Do you see anything happening in 120 s intervals?

If ath9k can't receive beacons in a 120 s interval, I would expect to
see delays also in the data path at the same time.

--
Kalle Valo


\
 
 \ /
  Last update: 2009-04-05 12:17    [W:0.128 / U:0.212 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site