wi0_cmd: busy bit won't clear

[Daniel Eischen]

On Sat, 6 Sep 2003, John Birrell wrote:

> On Tue, Aug 19, 2003 at 09:27:51AM -0600, M. Warner Losh wrote:
> > It seems that the new code sends out packets more quickly than the
> > old, and if you try to reset it while it has packets in flight, bad
> > things happen.  Or one thread is commanding the card to do something
> > that it doesn't like to reset out of.  There may be other issues as
> > well.
> 
> Has there been any progress on this?
> 
> I thought I ran into a similar problem today (wi0_cmd: busy bit won't clear)
> using an up-to-date current.
> 
> When I booted with the card plugged in, it would attach and ifconfig OK.
> Removing the card and reinserting it caused the "wi0_cmd: busy bit won't
> clear" when I went to ifconfig it.

Hmm, some of us get it in the reverse -- when the machine boots
with the card in, we get that message.  Removing and reinserting
the card after boot seems to work better, but perhaps that's
just my imagination -- I still sometimes have the same problem
when reinserting the card.

> The kernel I was booting had 'options BRIDGE' and the bridge sysctls were
> configured (from a hostap test I did before upgrading to current). The
> presence of the bridge code was enough to get an illegal channel warning
> when the card was inserted.
>
> After removing the bridge option, the card attaches, configs and detaches
> fine.

-- 
Dan Eischen