From owner-freebsd-stable@FreeBSD.ORG Sun Dec 14 19:26:58 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D642CA3; Sun, 14 Dec 2014 19:26:58 +0000 (UTC) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9105C38F; Sun, 14 Dec 2014 19:26:57 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id n3so7094018wiv.1 for ; Sun, 14 Dec 2014 11:26:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9J1VdjcdIXde7C3t76Qi6Le3gosSmEoUEXCP5u9LBQc=; b=hnmbClnmTSNLTwhWVYD8USFaN1J3VJqbUz0HNrqvTc4/kD+TnOmW5C9XocrgaHrr8j 7WOCszbKkDr7/HvvIDEyKSmK6jwAMFN0Khe5lAaR/SrJyaYKGB/ubw6d7WXoWXyw2Ewb CGB7YFQraGO71g+bycHjXCjsXs9NVuYpP+2do5YBs9apLHH4NDJAa1+szd6GUXJrX/Fx 0kWe2GXqBSRkKBH6fJiJQa4zW8nG7MEXZ5poglJALls4LhaaZx40cOjRl+6MEdTu4oHK iCd5yT5M5d3m0qJuee6KW9JN2Kae+lUnWh9q16xTjZgmIYndSRplpjp57B/zqx4hN+x6 4wNA== MIME-Version: 1.0 X-Received: by 10.194.24.103 with SMTP id t7mr46044349wjf.15.1418585214886; Sun, 14 Dec 2014 11:26:54 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Sun, 14 Dec 2014 11:26:54 -0800 (PST) In-Reply-To: References: <20141122171734.GA4600@marvin2011.fritz.box> <5470C695.3040204@yahoo.com.br> Date: Sun, 14 Dec 2014 11:26:54 -0800 X-Google-Sender-Auth: 9M1p1nJbYAd5_ng5IuMFDHzmY4c Message-ID: Subject: Re: ath(4) device timeout -> reboot necessary From: Adrian Chadd To: Thomas Zander Content-Type: text/plain; charset=UTF-8 Cc: Danilo Egea Gondolfo , FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2014 19:26:58 -0000 Hi, Nope. In theory the full reset is doing just that.. a full chip cold stop and start. There's only a handful of state that needs a full reset line pulldown to achieve. So if that's fixing it then ok, maybe there's some issues i can patch aronud by doing a full chip reset. I wonder if there are also some bugs lurking in some of the calibration code that keeps state over time; or the ANI code that keeps state over time. -adrian On 14 December 2014 at 09:23, Thomas Zander wrote: > On 23 November 2014 at 13:23, Thomas Zander wrote: >> On 22 November 2014 at 19:11, Adrian Chadd wrote: >> >>> Try setting >>> sysctl dev.ath.0.hal.force_full_reset=1 >> >> Thanks Adrian. I put this into sysctl.conf and observe the effects >> over the next weeks. > > I made the following observations in the past two weeks regarding this sysctl: > - Reboots are not strictly necessary after an ath0 device timeout to > get wifi to reconnect, as you expected, > - If a device timeout has happend once, it is a virtual certainty to > get the next one within 2 hours. This continues until the next reboot. > So *something* might not get reset fully > > Any ideas? > > Best regards > Riggs