Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith <Sujith.Manoharan@atheros.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: <lucisandor@gmail.com>,
	"ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] var/log/messages filling quickly
Date: Sun, 3 Jan 2010 11:51:25 +0530	[thread overview]
Message-ID: <19264.14181.214609.819450@gargle.gargle.HOWL> (raw)
In-Reply-To: <b6c5339f0912301049r773e083do6afd182eb7ad993c@mail.gmail.com>

Bob Copeland wrote:
> On Wed, Dec 30, 2009 at 9:42 AM, Lucian  andor <lucisandor@gmail.com> wrote:
> > Hi all,
> > I run an Ad-hoc network, using a SuSE 11.2 computer, kernel 2.6.32-5.5
> > from SuSE (probably modifed by them.) If I turn off all the other
> > computers in the network, the ath5k/kernel combination writes 20 times
> > per second to the system log /var/log/messages:
> >
> > Dec 28 14:10:31 battlecruiser kernel: [  929.933020] wlan0: No active
> > IBSS STAs - trying to scan for other IBSS networks with same SSID
> > (merge)
> 
> Turn off CONFIG_MAC80211_IBSS_DEBUG in the kernel config
> (or ask SuSE to do the same).  You can't turn it off at
> runtime, but you could turn off kernel debug messages in
> syslogd.
> 
> However, this is only supposed to happen every 30s if I
> read the code right.  Maybe someone on linux-wireless
> knows how this can happen?

This patch (in Linus' tree) apparently didn't make it to 2.6.32.

commit 450aae3d7b60a970f266349a837dfb30a539198b
Author: Sujith <Sujith.Manoharan@atheros.com>
Date:   Mon Nov 2 12:33:23 2009 +0530

    mac80211: Fix IBSS merge

    Currently, in IBSS mode, a single creator would go into
    a loop trying to merge/scan. This happens because the IBSS timer is
    rearmed on finishing a scan and the subsequent
    timer invocation requests another scan immediately.

    This patch fixes this issue by checking if we have just completed
    a scan run trying to merge with other IBSS networks.

    Signed-off-by: Sujith <Sujith.Manoharan@atheros.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>


Sujith

      reply	other threads:[~2010-01-03  6:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c775b4470912300642o2457d712m20dfb48c4c3508df@mail.gmail.com>
2009-12-30 18:49 ` [ath5k-devel] var/log/messages filling quickly Bob Copeland
2010-01-03  6:21   ` Sujith [this message]

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=19264.14181.214609.819450@gargle.gargle.HOWL \
    --to=sujith.manoharan@atheros.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lucisandor@gmail.com \
    --cc=me@bobcopeland.com \
    /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