From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 4 22:00:50 2005 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8932F16A4D0 for ; Tue, 4 Jan 2005 22:00:50 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 583E443D2D for ; Tue, 4 Jan 2005 22:00:50 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j04M0oSX092745 for ; Tue, 4 Jan 2005 22:00:50 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j04M0oKB092730; Tue, 4 Jan 2005 22:00:50 GMT (envelope-from gnats) Resent-Date: Tue, 4 Jan 2005 22:00:50 GMT Resent-Message-Id: <200501042200.j04M0oKB092730@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Matthias Buelow Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89D6D16A4CE for ; Tue, 4 Jan 2005 21:54:19 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50C4B43D53 for ; Tue, 4 Jan 2005 21:54:19 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j04LsJr8014755 for ; Tue, 4 Jan 2005 21:54:19 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j04LsJIT014750; Tue, 4 Jan 2005 21:54:19 GMT (envelope-from nobody) Message-Id: <200501042154.j04LsJIT014750@www.freebsd.org> Date: Tue, 4 Jan 2005 21:54:19 GMT From: Matthias Buelow To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: misc/75823: wi0 interface self-destructs after a couple hours (5.3-STABLE) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 22:00:50 -0000 >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@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: 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: