[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1238925174.4120.12.camel@localhost.localdomain>
Date: Sun, 05 Apr 2009 15:22:54 +0530
From: Jaswinder Singh Rajput <jaswinder@...nel.org>
To: Michael Buesch <mb@...sch.de>
Cc: Sujith <Sujith.Manoharan@...eros.com>,
wireless <linux-wireless@...r.kernel.org>,
David Miller <davem@...emloft.net>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: ath9k becon loss messages
On Sun, 2009-04-05 at 11:29 +0200, Michael Buesch wrote:
> > [ 1678.823011] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 1798.830589] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 1918.828044] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 2038.827224] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 2116.517152] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 2158.840243] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 2278.827427] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
>
>
> I think this message should only show if CONFIG_MAC80211_VERBOSE_DEBUG is set.
> It's kind of expected that we lose a beacon once in a while, so we shouldn't print
> verbose messages to the kernel log (even if they are KERN_DEBUG).
>
> 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
[ 1438.814157] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 1558.827336] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 1678.823011] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 1798.830589] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 1918.828044] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2038.827224] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2116.517152] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2158.840243] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2278.827427] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2398.827010] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2518.817295] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2638.821208] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2758.838757] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2878.825043] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 2998.828296] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3118.821456] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3238.813293] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3358.816763] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3478.820291] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3598.815145] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3718.814290] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3838.829043] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
[ 3958.817294] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
--
JSR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists