misc/75823: wi0 interface self-destructs after a couple hours (5.3-STABLE)

[Matthias Buelow]

>Number:         75823
>Category:       misc
>Synopsis:       wi0 interface self-destructs after a couple hours (5.3-STABLE)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 04 22:00:49 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Matthias Buelow
>Release:        5.3-STABLE
>Organization:
>Environment:
FreeBSD xxx 5.3-STABLE FreeBSD 5.3-STABLE #4: Fri Nov 19 22:15:57 CET 2004     root at xxx:/usr/obj/usr/src/sys/xxx  i386

>Description:
I've got a 3Com 3CRDW696 wifi card, which is supported by the wi driver.  When the device sees some usage for a couple hours (even with small, but more or less constant bandwidth consumption) the kernel starts spitting errors, and the device becomes unusable until the next reboot (ifconfig down/up won't help).


Device:

Jan  4 22:39:59 drjekyll kernel: wi0: <Intersil Prism2.5> mem 0xd8000000-0xd8000fff irq 17 at device 1.0 on pci3
Jan  4 22:39:59 drjekyll kernel: wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
Jan  4 22:39:59 drjekyll kernel: wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9)
Jan  4 22:39:59 drjekyll kernel: wi0: Ethernet address: 00:0d:54:aa:62:12
Jan  4 22:39:59 drjekyll kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps


Error messages:

Jan  4 19:53:37 drjekyll kernel: wi0: timeout in wi_cmd 0x010b; event status 0x8000
Jan  4 19:53:37 drjekyll kernel: wi0: xmit failed
Jan  4 19:53:37 drjekyll kernel: wi0: timeout in wi_seek to 127/0
Jan  4 19:53:38 drjekyll last message repeated 4 times
..
Jan  4 19:53:38 drjekyll kernel: wi0: bad alloc 127 != 13c, cur 1 nxt 2
Jan  4 20:42:31 drjekyll kernel: wi0: timeout in wi_seek to 127/0
Jan  4 20:42:32 drjekyll kernel: wi0: timeout in wi_seek to 127/0
Jan  4 21:01:30 drjekyll kernel: wi0: record read mismatch, rid=fd44, got=fd41
Jan  4 21:01:30 drjekyll kernel: wi0: failed in wi_seek to 0/0
Jan  4 21:01:30 drjekyll kernel: wi0: xmit failed
Jan  4 22:26:29 drjekyll kernel: wi0: device timeout
Jan  4 22:26:29 drjekyll kernel: wi0: wi_cmd: busy bit won't clear.
Jan  4 22:26:29 drjekyll kernel: wi0: init failed
Jan  4 22:26:29 drjekyll kernel: wi0: failed to allocate 2372 bytes on NIC
Jan  4 22:26:29 drjekyll kernel: wi0: tx buffer allocation failed (error 12)
Jan  4 22:26:29 drjekyll kernel: wi0: interface not running


The issue doesn't seem to appear with other systems on the same machine, so it doesn't look like the hardware is broken (at least not more broken than usually).

>How-To-Repeat:
      Install the above mentioned 3Com card, and run some traffic on it for lengthy periods of time (several hours).  Peer-to-peer traffic seems to be quite useful for demonstrating the problem.

>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted: