Return-path: Received: from mail-ia0-f170.google.com ([209.85.210.170]:61180 "EHLO mail-ia0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753371Ab3BHSsY (ORCPT ); Fri, 8 Feb 2013 13:48:24 -0500 Received: by mail-ia0-f170.google.com with SMTP id k20so4657282iak.29 for ; Fri, 08 Feb 2013 10:48:23 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Robert Shade Date: Fri, 8 Feb 2013 13:48:03 -0500 Message-ID: (sfid-20130208_195008_206593_D108785E) Subject: Re: Auth Packet TX Delay To: Adrian Chadd Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Maybe I have the terminology wrong, but I thought a cold reset meant toggling the PCI reset line. On Thu, Feb 7, 2013 at 4:40 PM, Adrian Chadd wrote: > On 7 February 2013 11:43, Robert Shade wrote: >> AR9160 / AR9106 > > Things are getting into a really odd state if that particular initial > calibration isn't finishing... > > Things I can think of: > > * There's some kind of noise going on that's angering the PHY (eg a spur); > * We should be doing a cold reset instead of a warm reset, upon a > channel change; (That fixes some issues I've seen on the AR9280 in > some environments); > * Bad/incorrectly hooked up antenans. > > From a software side, nothing much can be going wrong. as long as the > driver isn't doing something stupid like running multiple copies of > the reset / setup path on different CPUs/threads, it should be > reliable. > > HTH, > > > > Adrian