On Wed, Dec 30, 2009 at 9:42 AM, Lucian Șandor <[email protected]> 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?
--
Bob Copeland %% http://www.bobcopeland.com
Bob Copeland wrote:
> On Wed, Dec 30, 2009 at 9:42 AM, Lucian andor <[email protected]> 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 <[email protected]>
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 <[email protected]>
Signed-off-by: John W. Linville <[email protected]>
Sujith