cvs commit: src/sys/dev/iwi if_iwi.c if_iwivar.h

Luigi Rizzo rizzo at
Tue Feb 20 18:05:47 UTC 2007

On Tue, Feb 20, 2007 at 09:48:38AM -0800, Sam Leffler wrote:
> Luigi Rizzo wrote:
> > The fact that I am the only one seeing (or reporting) the problem
> > does not mean that there is no bug (or i wouldn't spend so much
> > time trying to fix it :).
> I'm not arguing this; I just don't like to see changes back-merged w/o a
> chance to settle.  I've used this driver for a lot and not hit the same
> issue you have.  Clearly fixing the cause of the lockup is important but
> it's also important to get to the root cause which appears to be
> elsewhere and likely related to an unstable signal quality.  I recall in

actually i don't think it is that - i am seeing the problem
even with the AP and the laptop in the same room.

Just to give a bit of context - my hardware is a Dell X1 laptop
with a 2200bg card operating at 2.4GHz, normally in G mode but
sometimes also with 11b access points.

The lockup occurred with a number of different APs (linksys WAG354,
digicom, hamlet, and another few unknown) and variable signal
strenghts (reporting anything from 34:0 to 85:0), with and without
other AP around).

> your original comparison of HEAD against RELENG_6 you found some other
> changes that hadn't been backported related to setting the receive

actually it was between the version of code before it was committed
to the tree (around jan 2006) and the one in the cvs now, and
it was for another bug i.e. the inability to retain the association
to a specific AP (digicom if i remember well).

> sensitivity and bluetooth coexistence.  You would do well to look at the
> latest linux code (at sourceforge which leads code going into the

doing that, in fact... digging in 12k lines of code!


More information about the cvs-src mailing list