wi0_cmd: busy bit won't clear

John Birrell jb at cimlogic.com.au
Sat Sep 6 01:26:41 PDT 2003

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.

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

John Birrell

More information about the freebsd-mobile mailing list