From owner-freebsd-stable@FreeBSD.ORG Tue Feb 21 18:33:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 B9F5E16A420 for ; Tue, 21 Feb 2006 18:33:00 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B5B443D67 for ; Tue, 21 Feb 2006 18:32:57 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k1LIWp7U013950; Tue, 21 Feb 2006 15:32:51 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: Sam Leffler Date: Tue, 21 Feb 2006 15:32:45 -0300 User-Agent: KMail/1.9.1 References: <200602210719.15683.joao@matik.com.br> <43FB3FB3.3010702@nurfuerspam.de> <43FB4905.2000506@errno.com> In-Reply-To: <43FB4905.2000506@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602211532.45889.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, Martin Subject: Re: hostap with atheros unusable on releng_6? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2006 18:33:00 -0000 On Tuesday 21 February 2006 14:08, Sam Leffler wrote: > I've got a ton of changes coming in from HEAD soon (don't recall what > the mfc date is). =A0These include a fix to deal with a race whereby tx > descriptors could be "lost" under heavy load. =A0This could explain the > slowdown in operation but not the timeouts. =A0If you can test with HEAD > that would be good; otherwise you'll need to wait for the mfc's. I agree but anyway the timeouts ocurre even when idle they seem to be time related (I know ... seems is bad) but I watched the lo= gs=20 on an idle AP and the device stops appearently after almost exact 30 minutes anyway, the happen under any kind of load even zero load Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br