From owner-freebsd-current@FreeBSD.ORG Mon Dec 1 17:41:37 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 E6C2B16A4CE for ; Mon, 1 Dec 2003 17:41:37 -0800 (PST) Received: from sage.ts.co.nz (sage.tasman.net [202.49.92.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76F8344011 for ; Mon, 1 Dec 2003 17:41:36 -0800 (PST) (envelope-from marcos@thepacific.net) Received: from sage.ts.co.nz (sage.ts.co.nz [202.49.92.1]) by sage.ts.co.nz (8.12.10/8.12.10) with ESMTP id hB21goHK021030; Tue, 2 Dec 2003 14:42:50 +1300 Received: from thepacific.net (gateway-nelson.thepacific.net [202.49.95.33]) by sage.ts.co.nz (8.12.10/8.12.10) with ESMTP id hB21dbcH020277; Tue, 2 Dec 2003 14:39:37 +1300 Message-ID: <3FCBED61.8080303@thepacific.net> Date: Tue, 02 Dec 2003 14:39:45 +1300 From: Marcos Biscaysaqu Organization: ThePacific.net User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Leo Bicknell , freebsd-current@freebsd.org References: <3FCBE05E.9090802@thepacific.net> <20031202012524.GA42747@ussenterprise.ufp.org> In-Reply-To: <20031202012524.GA42747@ussenterprise.ufp.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Atheros netstat error 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: Tue, 02 Dec 2003 01:41:38 -0000 Hi Leo. Thanks for the information, but do you know if is some thing to do to fix this? or simply I need wait for another driver version, because the driver looks so much better than a couple a week ago, the only bad thing is this problem and when happen kill all the wireless network Thanks Leo Bicknell wrote: >In an effort to cut down on Sam's load... > >This is a known issue. Evidently there are some low level radio >counters that are incorrectly being reported as input errors. >Basically they should be ignored until the driver can be changed >to not report them. > > > > -- Marcos Biscaysaqu Systems Administrator ThePacific.Net Ltd.