From owner-freebsd-current@FreeBSD.ORG Fri Jun 20 22:04:22 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 9BF4F37B401 for ; Fri, 20 Jun 2003 22:04:22 -0700 (PDT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id D070C43F85 for ; Fri, 20 Jun 2003 22:04:21 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id MUA74016; Fri, 20 Jun 2003 22:04:20 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 6CF955D04; Fri, 20 Jun 2003 22:04:19 -0700 (PDT) To: BSDVault In-Reply-To: Message from BSDVault of "Sat, 21 Jun 2003 00:32:45 EDT." Date: Fri, 20 Jun 2003 22:04:19 -0700 From: "Kevin Oberman" Message-Id: <20030621050419.6CF955D04@ptavv.es.net> cc: freebsd-current@freebsd.org Subject: Re: Wi driver has WEP issues on both 5.0 and 5.1 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: Sat, 21 Jun 2003 05:04:22 -0000 > Date: Sat, 21 Jun 2003 00:32:45 -0400 > From: BSDVault > Sender: owner-freebsd-current@freebsd.org > > A head up about the wi driver in FreeBSD 5.0 and 5.1. I have a netgear > MA-311 card that supports HostAP mode. The issue is that I get a busy bit > error. The exact error starts with the following.. THIS ONLY OCCURS WHEN > WEP IS ENABLED: > > wi0: timeout in wi_seek to fc00/0; last status 800b > > We then move on to : > > wi0: wi_cmd: busy bit won't clear. > > This seems to cycle until the next error: > > wi0: failed to allocate 1594 bytes on NIC > wi0: tx buffer allocation failed > wi0: mgmt. Buffer allocation failed > > Then back through the entire error sequence again. Eventually the box will > freeze as these errors cycle and then free up again when it starts back at > the timeout error. I was hopeful that the new wi driver in 5.1 would > address this problem as I know several persons with Prism chipsets that have > this very same issue on 5.0 and 5.1. > > Please respond directly as I am not on -current mailing list. I have seen the same ting, but only when three is an attempt to associate with an AP that has a different WEP key. It can happen with either 40 or 108 bit encryption. As a result, I now build my kernel without the wi driver and only load it when I need it. I don't know if Warner has seen this. Cross-post to FreeBSD lists is frowned upon, but I am tempted to send this to mobile. It's where these issues are most heavily discussed. I'm not sure if I ever saw this with V4.6 or 4.7. I have seen it on V5 since I moved to current late last year. -- 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