From owner-freebsd-stable@FreeBSD.ORG Sat Aug 23 16:46:14 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F2F216A4BF for ; Sat, 23 Aug 2003 16:46:14 -0700 (PDT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1DCF43F85 for ; Sat, 23 Aug 2003 16:46:13 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id MUA74016 for ; Sat, 23 Aug 2003 16:46:11 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 95C475D04 for ; Sat, 23 Aug 2003 16:46:10 -0700 (PDT) To: freebsd-stable@freebsd.org In-Reply-To: Message from Peter Radcliffe of "Sat, 23 Aug 2003 14:50:56 EDT." <20030823185056.GB26960@pir.net> Date: Sat, 23 Aug 2003 16:46:10 -0700 From: "Kevin Oberman" Message-Id: <20030823234610.95C475D04@ptavv.es.net> Subject: Re: prism 2.5 mini-pci issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2003 23:46:14 -0000 > Date: Sat, 23 Aug 2003 14:50:56 -0400 > From: Peter Radcliffe > Sender: owner-freebsd-stable@freebsd.org > > I tried my intel/xircom prism 2.5 mini-pci card again, yesterday, > with -stable. > > wi0: mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci1 > wi0: 802.11 address: 00:05:3c:06:34:c9 > wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) > wi0: Intersil Firmware: Primary 1.01.00, Station 1.04.09 > > It behaved itself for a while and then got very unhappy; > > wi0: timeout in wi_cmd 0x010b; event status 0x0000 > wi0: xmit failed > wi0: watchdog timeout > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: init failed > wi0: timeout in wi_seek to fc07/0; last status 800b > wi0: timeout in wi_seek to fc00/0; last status 800b > wi0: timeout in wi_seek to fc81/0; last status 800b > wi0: timeout in wi_seek to fc83/0; last status 800b > wi0: timeout in wi_cmd 0x010b; event status 0x0000 > wi0: xmit failed > wi0: watchdog timeout > wi0: timeout in wi_cmd 0x0002; event status 0x0000 > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: init failed > > The machine hung up for a little while during some of the failures but > after it started having issues it never really recovered. Was WEP enabled? Were you associated with an access point at the time? While this problem has been reported by others under different circumstances, I have been able to run reliably by removing "device wi" from my kernel and only loading it when I am going to use it. Otherwise I got the same lock-up which would eventually force me to reboot. I know imp has been working on this (read mobile and current archives for more history). I just hope that this might help a bit. I have never had a problem when I have actually had the interface in use...only when NOT using it. It is almost certainly caused by interference of some sort. For example, I never had this problem except in my office in Berkeley. In my main work location it never caused a problem. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634