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

[Brian Candler]

>Number:         73871
>Category:       kern
>Synopsis:       Intersil Prism wireless wi0 locks up, "busy bit won't clear"
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov 12 14:20:16 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Brian Candler
>Release:        FreeBSD 5.3-RELEASE i386
>Organization:
>Environment:
System: FreeBSD thinkdog.local.linnet.org 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sun Nov 7 10:30:04 GMT 2004 root at thinkdog.local.linnet.org:/usr/src/sys/i386/compile/THINKDOG i386

This is an IBM Thinkpad X30 laptop with an internal mini-PCI wireless card,
detected as wi0.

[pciconf -l -v]
wi0 at pci1:2:0:   class=0x028000 card=0x25138086 chip=0x38731260 rev=0x01 hdr=0x00
    vendor   = 'Intersil Americas Inc (Was: Harris Semiconductor)'
    device   = 'PRISM 2.5 802.11b 11Mbps Wireless Controller'
    class    = network

[dmesg]
wi0: <Intersil Prism2.5> mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci1
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9)
wi0: Ethernet address: 00:05:3c:09:7e:9d
wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps

>Description:

After some use, the card locks up and the problem cannot be cleared without
rebooting the machine.

Nov 12 14:00:44 thinkdog kernel: wi0: timeout in wi_cmd 0x010b; event status 0x8000
Nov 12 14:00:44 thinkdog kernel: wi0: xmit failed
Nov 12 14:00:44 thinkdog kernel: wi0: timeout in wi_seek to 127/0
Nov 12 14:00:44 thinkdog last message repeated 3 times
Nov 12 14:00:44 thinkdog kernel: wi0: wi_cmd: busy bit won't clear.

This has happened to me twice in a couple of days. The first time I had
ifconfig powersave set, so I removed it; but it's now happened again without
powersave enabled.

Once it's in this state, no further 802.11 or IP configuration commands are
accepted. For example:

bash-2.05b# ifconfig wi0 powersave
ifconfig: SIOCS80211: Operation not supported by device
bash-2.05b# ifconfig wi0 wepmode on
ifconfig: SIOCS80211: Operation not supported by device
bash-2.05b# ifconfig wi0 1.2.3.4
ifconfig: ioctl (SIOCAIFADDR): Operation not supported by device


>How-To-Repeat:
[/etc/rc.conf]
ifconfig_wi0="DHCP"
[/etc/start_if.wi0]
ifconfig wi0 wepmode on wepkey 0xNNNNNNNNNN # powersave

Then use it fairly heavily (a 'unison' dump of files across the LAN triggered
it the last time)

>Fix:

Sorry, don't know. But I think it should at least recover gracefully, even
if there's a problem with the hardware.
>Release-Note:
>Audit-Trail:
>Unformatted: