I am trying to get a Cisco Aironet 802.11b PCI adaptor running in
-current.  The PCMCIA version of this product works like a champ, but
the PCI version suffers device timeouts and very sluggish operation.

    Jun 12 17:48:54 capsicum /netbsd: an0 at pci0 dev 13 function 0: Cisco/Aironet Wireless Communications Cisco/Aironet PCI352 PCI Wireless LAN Adapter
    Jun 12 17:48:54 capsicum /netbsd: an0: interrupting at irq 9
    Jun 12 17:48:54 capsicum /netbsd: an0: command busy
    Jun 12 17:48:54 capsicum /netbsd: an0: 802.11 address: 00:40:96:xx:xx:xx
    Jun 12 17:48:54 capsicum /netbsd: an0: failed to enable MAC
    Jun 12 17:49:03 capsicum /netbsd: an0: device timeout
    Jun 12 17:49:25 capsicum /netbsd: an0: device timeout
    Jun 12 17:52:57 capsicum /netbsd: an0: device timeout
    Jun 12 17:53:18 capsicum /netbsd: an0: device timeout
    Jun 12 17:54:22 capsicum /netbsd: an0: device timeout
    Jun 12 17:54:36 capsicum /netbsd: an0: device timeout
    Jun 12 17:56:09 capsicum /netbsd: an0: device timeout

I'm kind of at a loss as to how to track this down.  There are 3 other
devices on irq 9.  Could the devices that are looked at first in the
chained interrupt routines be "stealing" the interrupt and causing the
whole "chained interrupts" to return early (eg. before the an0 driver
gets called?)

I'm grasping at straws, but since the code works fine for the other
cards I suspect a really simple problem somewhere.  Any ideas or
hints?

-wolfgang
-- 
       Wolfgang Rupprecht <wolfgang+gnus@dailyplanet.wsrcc.com>
		    http://www.wsrcc.com/wolfgang/
Coming soon: GPS mapping tools for Open Systems. http://www.gnomad-mapping.com/