From owner-freebsd-current@FreeBSD.ORG  Fri Jun 20 21:31:25 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 AE89337B401
	for <freebsd-current@freebsd.org>;
	Fri, 20 Jun 2003 21:31:25 -0700 (PDT)
Received: from central.ixn.com (central.ixn.com [65.19.132.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4DEBE43F93
	for <freebsd-current@freebsd.org>;
	Fri, 20 Jun 2003 21:31:25 -0700 (PDT)
	(envelope-from diesel@bsdvault.net)
Received: from [172.16.1.4] (va-sterlingISP-61.strgva.adelphia.net
	[68.70.163.61])
	by central.ixn.com (8.12.9/8.12.9) with ESMTP id h5L4Yhhc023422
	for <freebsd-current@freebsd.org>;
	Sat, 21 Jun 2003 00:34:43 -0400 (EDT)
User-Agent: Microsoft-Entourage/10.1.1.2418
Date: Sat, 21 Jun 2003 00:32:45 -0400
From: BSDVault <diesel@bsdvault.net>
To: <freebsd-current@freebsd.org>
Message-ID: <BB19582D.2875%diesel@bsdvault.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Status: No, hits=0.0 required=6.8
	tests=SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_ENTOURAGE
	version=2.44
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jun 2003 04:31:26 -0000

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.

Thanks 

Ray