kern/73871: Intersil Prism wireless wi0 locks up, "busy bit won't clear"

Brian Candler B.Candler at pobox.com
Wed May 11 10:10:07 GMT 2005


The following reply was made to PR kern/73871; it has been noted by GNATS.

From: Brian Candler <B.Candler at pobox.com>
To: bug-followup at FreeBSD.org
Cc:  
Subject: Re: kern/73871: Intersil Prism wireless wi0 locks up, "busy bit won't clear"
Date: Wed, 11 May 2005 10:46:48 +0100

 Supplementary information.
 
 I can make the interface lockup immediately when in a busy wireless
 environment (multiple access points and ssids).
 
 # kldload if_wi
 May 11 10:07:45 thinkdog kernel: wi0: <Intersil Prism2.5> mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci1
 May 11 10:07:45 thinkdog kernel: wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
 May 11 10:07:45 thinkdog kernel: wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9)
 May 11 10:07:45 thinkdog kernel: wi0: Ethernet address: 00:05:3c:09:7e:9d
 May 11 10:07:45 thinkdog kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
 # ifconfig wi0 up
 # ifconfig wi0 ssid 'somessid'
 May 11 10:08:24 thinkdog kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8008
 May 11 10:08:24 thinkdog kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8008
 May 11 10:08:24 thinkdog kernel: wi0: wi_cmd: busy bit won't clear.
 May 11 10:08:24 thinkdog kernel: wi0: init failed
 May 11 10:08:24 thinkdog kernel: wi0: failed to allocate 2372 bytes on NIC
 May 11 10:08:24 thinkdog kernel: wi0: tx buffer allocation failed (error 12)
 May 11 10:08:24 thinkdog kernel: wi0: interface not running
 
 The commands have to be given in this order to cause the lockup. If instead
 I do:
 
 # kldload if_wi
 # ifconfig wi0 ssid 'somessid'
 # ifconfig wi0 up
 
 then it appears to associate.
 
 Taking the interface down and up a few times, I can get into a state where
 consistently 'ifconfig wi0 down' causes an error:
 
 # ifconfig wi0 down
 May 11 10:25:32 thinkdog kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8008
 
 However it's possible then to bring the interface back up.
 
 I have also had some problems where the client fails to associate with the
 access point until I kldunload/kldload the module again, but this may be a
 problem with the particular AP I'm working with.
 
 Regards,
 
 Brian.


More information about the freebsd-bugs mailing list