[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090331122348.GA31324@hash.localnet>
Date: Tue, 31 Mar 2009 08:23:48 -0400
From: Bob Copeland <me@...copeland.com>
To: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Cc: Jiri Slaby <jirislaby@...il.com>,
Dhaval Giani <dhaval.lists@...gianis.in>,
linville@...driver.com, davem@...emloft.net,
linux-wireless@...r.kernel.org, ath5k-devel@...ema.h4ckr.net,
Nick Kossifidis <mickflemm@...il.com>,
"Luis R. Rodriguez" <lrodriguez@...eros.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] ath5k: fix hw rate index condition
On Tue, Mar 31, 2009 at 09:21:40AM +0530, Dhaval Giani wrote:
> Am not sure what the PID controller is, and google gave me a number of
> results, which did not make too much sense in the context.
CONFIG_MAC80211_RC_PID -- unfortunately I recall having to jump through
a few config hoops to enable it.
> One way I have found of reproducing it is to connect to open networks,
> but it does not happen always. At home, when my network is set to open,
> I do not see this issue, whereas at the airport, kaboom.
Ok - that is a useful data point. Perhaps something to do with the rates
the peer supports; it would help if you could grab a scan next time you
are in the area. Turn off auto-connect to open networks, then do:
# iw dev wlan0 scan trigger
# iw dev wlan0 scan dump >> dump.out # do this a few times
Then if a particular peer triggers the problem, we can look at the
advertised rates to see if anything jumps out.
--
Bob Copeland %% www.bobcopeland.com
--
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