From: Michael Buesch <mb@bu3sch.de>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Sujith <Sujith.Manoharan@atheros.com>,
wireless <linux-wireless@vger.kernel.org>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ath9k becon loss messages
Date: Sun, 5 Apr 2009 11:29:38 +0200 [thread overview]
Message-ID: <200904051129.38904.mb@bu3sch.de> (raw)
In-Reply-To: <1238923439.4120.9.camel@localhost.localdomain>
On Sunday 05 April 2009 11:23:59 Jaswinder Singh Rajput wrote:
> With latest linus tree I am getting, .config file attached:
>
> [ 22.895051] r8169: eth0: link down
> [ 22.897564] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 22.928047] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 22.982292] libvirtd used greatest stack depth: 4200 bytes left
> [ 63.709879] wlan0: authenticate with AP 00:11:95:9e:df:f6
> [ 63.712096] wlan0: authenticated
> [ 63.712127] wlan0: associate with AP 00:11:95:9e:df:f6
> [ 63.726831] wlan0: RX AssocResp from 00:11:95:9e:df:f6 (capab=0x471 status=0 aid=1)
> [ 63.726855] wlan0: associated
> [ 63.730093] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [ 74.296087] wlan0: no IPv6 routers present
> [ 79.349044] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 119.358200] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 179.354292] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 259.366044] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 359.348292] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 361.953459] packagekitd used greatest stack depth: 4160 bytes left
> [ 478.824258] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 598.813343] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 718.817292] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 838.824567] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 958.815402] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> [ 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
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.
--
Greetings, Michael.
next prev parent reply other threads:[~2009-04-05 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 9:23 ath9k becon loss messages Jaswinder Singh Rajput
2009-04-05 9:29 ` Michael Buesch [this message]
2009-04-05 9:36 ` Michael Buesch
2009-04-05 10:03 ` Kalle Valo
2009-04-05 11:00 ` Jaswinder Singh Rajput
2009-04-05 9:52 ` Jaswinder Singh Rajput
2009-04-05 10:13 ` Kalle Valo
2009-04-06 7:14 ` Helmut Schaa
2009-04-06 8:17 ` Kalle Valo
2009-04-06 8:56 ` Helmut Schaa
2009-04-06 9:04 ` Kalle Valo
2009-04-06 10:17 ` Michael Buesch
2009-04-06 10:23 ` Kalle Valo
2009-04-06 10:51 ` Helmut Schaa
2009-04-06 11:05 ` Kalle Valo
2009-04-06 15:18 ` Kalle Valo
2009-04-06 18:00 ` John W. Linville
2009-04-07 5:54 ` Kalle Valo
2009-04-07 13:53 ` John W. Linville
2009-04-07 15:19 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904051129.38904.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Sujith.Manoharan@atheros.com \
--cc=davem@davemloft.net \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).