Re: "scan stuck" with if_iwi(4)

2006-08-01 Thread Brooks Davis
On Thu, Jul 27, 2006 at 04:47:16PM -0700, Sam Leffler wrote: > Andrew Thompson wrote: > > On Wed, Jul 26, 2006 at 01:28:12PM -0700, Sam Leffler wrote: > >> Henrik Brix Andersen wrote: > >>> Oh? Sounds interesting, where can I find these patches? > >> The work has always been in perforce.freebsd.org

Re: "scan stuck" with if_iwi(4)

2006-07-27 Thread Sam Leffler
Sam Leffler wrote: > Andrew Thompson wrote: >> On Wed, Jul 26, 2006 at 01:28:12PM -0700, Sam Leffler wrote: >>> Henrik Brix Andersen wrote: Oh? Sounds interesting, where can I find these patches? >>> The work has always been in perforce.freebsd.org; look in the sam_wifi >>> branch. The code w

Re: "scan stuck" with if_iwi(4)

2006-07-27 Thread Sam Leffler
Andrew Thompson wrote: > On Wed, Jul 26, 2006 at 01:28:12PM -0700, Sam Leffler wrote: >> Henrik Brix Andersen wrote: >>> Oh? Sounds interesting, where can I find these patches? >> The work has always been in perforce.freebsd.org; look in the sam_wifi >> branch. The code will not hit head until fol

Re: "scan stuck" with if_iwi(4)

2006-07-26 Thread Andrew Thompson
On Wed, Jul 26, 2006 at 01:28:12PM -0700, Sam Leffler wrote: > Henrik Brix Andersen wrote: > > > > Oh? Sounds interesting, where can I find these patches? > > The work has always been in perforce.freebsd.org; look in the sam_wifi > branch. The code will not hit head until folks show up to fix le

Re: "scan stuck" with if_iwi(4)

2006-07-26 Thread Sam Leffler
Henrik Brix Andersen wrote: > On Wed, Jul 26, 2006 at 11:07:36AM -0700, Sam Leffler wrote: >> Sure, it was for others. > > Ah :) > >> Which version are you looking at? The numbers in iwi are from the code >> in linux-2.6.17; maybe it's been changed again in the code on >> sourceforge? > > I was

Re: "scan stuck" with if_iwi(4)

2006-07-26 Thread Henrik Brix Andersen
On Wed, Jul 26, 2006 at 11:07:36AM -0700, Sam Leffler wrote: > Sure, it was for others. Ah :) > Which version are you looking at? The numbers in iwi are from the code > in linux-2.6.17; maybe it's been changed again in the code on > sourceforge? I was looking in the ipw2200.h header file from ip

Re: "scan stuck" with if_iwi(4)

2006-07-26 Thread Sam Leffler
Henrik Brix Andersen wrote: > On Wed, Jul 26, 2006 at 09:10:03AM -0700, Sam Leffler wrote: >> Thanks for your help but understand this is not necessarily a solution; >> just the addition of a knob. > > I know. Sure, it was for others. > >> The linux driver already used 7 consecutive beacon miss

Re: "scan stuck" with if_iwi(4)

2006-07-26 Thread Henrik Brix Andersen
On Wed, Jul 26, 2006 at 09:10:03AM -0700, Sam Leffler wrote: > Thanks for your help but understand this is not necessarily a solution; > just the addition of a knob. I know. > The linux driver already used 7 consecutive beacon misses to trigger > roaming so I'm not sure why 10 is an improvement b

Re: "scan stuck" with if_iwi(4)

2006-07-26 Thread Sam Leffler
Henrik Brix Andersen wrote: > On Thu, Jul 20, 2006 at 04:01:20PM -0700, Sam Leffler wrote: >> The basic problem is your card is losing sync w/ the ap. I don't know >> what the local conditions are but I've seen this a lot w/ iwi; there's >> nothing we can do in the driver if you want to be able to

Re: "scan stuck" with if_iwi(4)

2006-07-26 Thread Henrik Brix Andersen
On Thu, Jul 20, 2006 at 04:01:20PM -0700, Sam Leffler wrote: > The basic problem is your card is losing sync w/ the ap. I don't know > what the local conditions are but I've seen this a lot w/ iwi; there's > nothing we can do in the driver if you want to be able to roam. Update: this was just fix

Re: "scan stuck" with if_iwi(4)

2006-07-20 Thread Henrik Brix Andersen
On Thu, Jul 20, 2006 at 04:01:20PM -0700, Sam Leffler wrote: > You will not be able to reproduce the problem because the code in 6.1R > ignored beacon misses (and a lot of other things). I see. > The stuck scan is not fatal; the driver just resets the card. It's > caused by a firwmare problem th

Re: "scan stuck" with if_iwi(4)

2006-07-20 Thread Henrik Brix Andersen
On Fri, Jul 21, 2006 at 09:00:06AM +1000, Mark Andrews wrote: > > The iwi code was recently MFC and it required a port change > iwi-firmware -> iwi-firmware-kmod. Depending on when you > upgraded the src and ports you may not have seen the ports > change. Yeah, I know - I

Re: "scan stuck" with if_iwi(4)

2006-07-20 Thread Sam Leffler
Mark Andrews wrote: > The iwi code was recently MFC and it required a port change > iwi-firmware -> iwi-firmware-kmod. Depending on when you > upgraded the src and ports you may not have seen the ports > change. > > Mark > > B.T.W. the new code is more stable

Re: "scan stuck" with if_iwi(4)

2006-07-20 Thread Sam Leffler
Henrik Brix Andersen wrote: > Hi, > > I recently upgraded my IBM ThinkPad X31 from 6.1-RELEASE to 6.1-STABLE > after which the if_iwi(4) driver started dropping the connection at > regular intervals when connected to my hostapd-based AP using WPA2 PSK > CCMP. > > The dmesg output with debug.iwi=4

Re: "scan stuck" with if_iwi(4)

2006-07-20 Thread Mark Andrews
The iwi code was recently MFC and it required a port change iwi-firmware -> iwi-firmware-kmod. Depending on when you upgraded the src and ports you may not have seen the ports change. Mark B.T.W. the new code is more stable for me. No more comple

"scan stuck" with if_iwi(4)

2006-07-20 Thread Henrik Brix Andersen
Hi, I recently upgraded my IBM ThinkPad X31 from 6.1-RELEASE to 6.1-STABLE after which the if_iwi(4) driver started dropping the connection at regular intervals when connected to my hostapd-based AP using WPA2 PSK CCMP. The dmesg output with debug.iwi=4 is listed below - it fails regularly (every