From owner-freebsd-current@FreeBSD.ORG Wed Sep 30 03:54:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7190C1065672; Wed, 30 Sep 2009 03:54:01 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4797A8FC12; Wed, 30 Sep 2009 03:54:01 +0000 (UTC) Received: from Macintosh-4.local ([10.0.0.198]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n8U3s0bO012483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Sep 2009 20:54:00 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <4AC2D658.8070908@freebsd.org> Date: Tue, 29 Sep 2009 20:54:00 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Alex Dupre References: <4AC0BB4A.40201@FreeBSD.org> <4AC17F33.80800@freebsd.org> <4AC1ABE5.6090409@FreeBSD.org> In-Reply-To: <4AC1ABE5.6090409@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: Atheros 9280 issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 30 Sep 2009 03:54:01 -0000 Alex Dupre wrote: > Sam Leffler wrote: >>> Clients can connect to the AP, but obviously packets are dropped every >>> time the card is reset. >> >> How do you know packets are dropped? Nothing should be lost. > > I'm pinging the access point from an associated wifi client: when this > message appears one or two pings are lost. Previously, when such > messages didn't appear, no pings were lost. Maybe the reply timeouts and > is not completely lost, I'll do more tests asap. I thought reset didn't lose any frames but perhaps not. athdebug reset should (I think) tell you if frames are lost. > >> "every few seconds" is not helpful. > > Actually the timing is highly variable, it may happen once a second, > like once every 15 seconds or more. Usually (in the two hours I tried) > every 2-5 seconds. > >> Look for something else in the >> system that coincides w/ your msgs. It's possible that periodic >> calibration done by the driver has a bad effect; you can turn it off by >> setting a sysctl (look at sysctl -a and/or the driver code). > > hw.ath.shortcal = 0, right? > > I'll try, I haven't done additional tests before knowing what would be > useful for debugging. Actually it looks like hw.ath.longcal=0 is what you want. Sam