From owner-freebsd-current@FreeBSD.ORG Tue Dec 30 21:57:18 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F22916A4CE for ; Tue, 30 Dec 2003 21:57:18 -0800 (PST) Received: from quelrod.quelrod.net (cs24243230-109.austin.rr.com [24.243.230.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56D7543D5E for ; Tue, 30 Dec 2003 21:57:16 -0800 (PST) (envelope-from quel@quelrod.net) Received: from quelrod.net (quelrod.net [127.0.0.1]) by quelrod.quelrod.net (8.12.9/8.12.9) with ESMTP id hBV5vTm2007747 for ; Tue, 30 Dec 2003 23:57:29 -0600 (CST) Received: from localhost (quel@localhost) by quelrod.net (8.12.9/8.12.9/Submit) with ESMTP id hBV5vTvU027965 for ; Tue, 30 Dec 2003 23:57:29 -0600 (CST) Date: Tue, 30 Dec 2003 23:57:28 -0600 (CST) From: quel@quelrod.net To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: wi driver failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2003 05:57:18 -0000 I have found a rather strange bug w/ the wi driver (pcmcia card.) After I have been on a wireless network for a while, usually around 3.5hours or greater all of sudden the association drops and I get the following: Dec 30 23:02:31 thor kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8009 Dec 30 23:02:31 thor kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8009 Dec 30 23:02:32 thor kernel: wi0: wi_cmd: busy bit won't clear. Dec 30 23:02:32 thor kernel: wi0: init failed Dec 30 23:02:32 thor kernel: wi0: failed to allocate 2372 bytes on NIC Dec 30 23:02:32 thor kernel: wi0: tx buffer allocation failed (error 12) Dec 30 23:02:32 thor kernel: wi0: interface not running ejecting and reinserting the card only causes more of these errors when i try to dhcp or other send a packet. The "fix" is resetting the ap. It is a rather old AP but I'm fairly certain that freebsd needs to somehow trap this problem. I'm going to try to find packet logs of this phenomenon but have been unsuccessful so far. -James Nobis