wi (hostap) issues, 3.2-stable

[matthew <matt_(_at_)_ice-nine_(_dot_)_org>]

    Using a soekris NET4521 running a slim OpenBSD 3.2 release as
  a wireless AP in what is essentially a repeater setup. (system
  has a wireless uplink to the network, and provides customers
  with a wireless AP on the 'internal' (other) side)

  [ network PoP ] <-----> wi1   wi0 <-----> [ customers ]

    At unpredictable times the hostap wi interface will seize and
  not pass traffic, failure mode looks like this:
-----
Jan  6 12:16:29 host /bsd: wi0: wi_mgmt_xmit: xmit failed
Jan  6 12:16:29 host /bsd: wi0: wi_start: xmit failed
Jan  6 12:16:29 host /bsd: wi0: wi_mgmt_xmit: xmit failed
Jan  6 12:17:02 host /bsd: wi0: device timeout
Jan  6 12:17:03 host /bsd: wi0: wi_mgmt_xmit: xmit failed
Jan  6 12:17:03 host last message repeated 14 times 
Jan  6 12:17:03 host /bsd: wi0: init failed
Jan  6 12:17:03 host /bsd: wi0: failed to allocate 1594 bytes on NIC 
Jan  6 12:17:03 host /bsd: wi0: tx buffer allocation failed
Jan  6 12:17:03 host /bsd: wi0: failed to allocate 1594 bytes on NIC
Jan  6 12:17:03 host /bsd: wi0: mgmt. buffer allocation failed
Jan  6 12:18:03 host /bsd: wi0: wi_cmd failed with 60
Jan  6 12:19:03 host /bsd: wi0: wi_cmd failed with 60
[ ifconfig wi0 down; ifconfig wi0 up happens here ]
Jan  6 12:24:54 host /bsd: wi0: init failed
Jan  6 12:24:54 host /bsd: wi0: failed to allocate 1594 bytes on NIC
Jan  6 12:24:54 host /bsd: wi0: tx buffer allocation failed
Jan  6 12:24:54 host /bsd: wi0: failed to allocate 1594 bytes on NIC 
Jan  6 12:24:54 host /bsd: wi0: mgmt. buffer allocation failed
Jan  6 12:25:20 host reboot: rebooted by root
-----

    A simple 'ifconfig wi0 down; ifconfig wi0 up' does not seem
  to rectify the problem. Is it possible that traffic load is
  leading to this situation? The card is a Prism II with what I
  understand is recent firmware revisions (linksys):

  PRISM 2.5 ISL3873, Firmware 1.1.0 (primary), 1.4.9 (station)

    I realize the data I can provide is not ideal; I am curious
  if anyone else has seen similar problems. dmesg below, I'll happily
  provide any other details (including the kernel configuration) on
  request.

    It will be difficult to capture debug output (ifconfig wi0 debug)
  surrounding this event simply because I can't predict when it
  occurs.

  I also don't know if it is related to this bug:
  http://groups.google.com/groups?th=7cd6e3bc57c48dfe&rnum=2

  Anyone have some insight here?
  Thanks
  matthew

-------
OpenBSD 3.2-stable (NEDERNET) #0: Sat Jan  4 00:29:11 MST 2003
    matt_(_at_)_iorek:/usr/src/sys/arch/i386/compile/NEDERNET
cpu0: AMD Am5x86 W/B 133/160 ("AuthenticAMD" 486-class)
cpu0: FPU
real mem  = 66695168 (65132K)
avail mem = 59740160 (58340K)
using 839 buffers containing 3436544 bytes (3356K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 20/21/13, BIOS32 rev. 0 @ 0xf00c0
pcibios0 at bios0: rev. 2.0 @ 0xf0000/0x10000
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc8000/0xa000
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "AMD ElanSC520 Host-PCI" rev 0x00
cbb0 at pci0 dev 17 function 0 "Texas Instruments PCI1420 PCI-CardBus" rev 0x00: irq 10
cbb1 at pci0 dev 17 function 1 "Texas Instruments PCI1420 PCI-CardBus" rev 0x00: irq 10
sis0 at pci0 dev 18 function 0 "NS DP83815 10/100" rev 0x00: irq 11 address 00:00:24:c0:a0:e4
nsphyter0 at sis0 phy 0: DP83815 10/100 integrated, rev. 1
sis1 at pci0 dev 19 function 0 "NS DP83815 10/100" rev 0x00: irq 5 address 00:00:24:c0:a0:e5
nsphyter1 at sis1 phy 0: DP83815 10/100 integrated, rev. 1
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 1 device 0 cacheline 0x10, lattimer 0x3f
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 2 device 0 cacheline 0x10, lattimer 0x3f
pcmcia1 at cardslot1
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
wdc0 at isa0 port 0x1f0/8 irq 14
wd0 at wdc0 channel 0 drive 0: <SanDisk SDCFB-64>
wd0: 1-sector PIO, LBA, 61MB, 490 cyl, 8 head, 32 sec, 125440 sectors
wd0(wdc0:0:0): using BIOS timings
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom0: console
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
biomask 4400 netmask 4c20 ttymask 4c22
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
wi0 at pcmcia0 function 0 "INTERSIL, HFA384x/IEEE, Version 01.02" port 0xa000/64
wi0: PRISM 2.5 ISL3873, Firmware 1.1.0 (primary), 1.4.9 (station), address 00:02:6f:03:5f:b0
wi1 at pcmcia1 function 0 "Lucent Technologies, WaveLAN/IEEE, Version 01.01" port 0xa400/64
wi1: Firmware 7.28 variant 1, address 00:02:2d:5e:43:de