From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 22 23:19:58 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC0531065670; Thu, 22 Dec 2011 23:19:58 +0000 (UTC) (envelope-from adrian@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AC6878FC08; Thu, 22 Dec 2011 23:19:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBMNJw7q003894; Thu, 22 Dec 2011 23:19:58 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBMNJwJD003890; Thu, 22 Dec 2011 23:19:58 GMT (envelope-from adrian) Date: Thu, 22 Dec 2011 23:19:58 GMT Message-Id: <201112222319.pBMNJwJD003890@freefall.freebsd.org> To: graham@menhennitt.com.au, adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Cc: Subject: Re: kern/143868: [ath] [patch] [request] allow Atheros watchdog timeout to be tunable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2011 23:19:58 -0000 Synopsis: [ath] [patch] [request] allow Atheros watchdog timeout to be tunable State-Changed-From-To: open->closed State-Changed-By: adrian State-Changed-When: Thu Dec 22 23:19:14 UTC 2011 State-Changed-Why: Submitter reports thus: == The Soekris box net5501 I use as my router/WAP/server used to report timeouts every few seconds. I upped that timeout value by changing the code to fix it (well, actually, reduce it to a managable level). It seemed that this should be tunable via a sysctl instead. I've added a second antenna for diversity and that seems to have fixed the problem completely. So, I don't need it any longer. == This is a common problem - if not all antennas are configured, the radio/baseband can incorrectly calibrate things and it shows up as a "stuck beacon". http://www.freebsd.org/cgi/query-pr.cgi?pr=143868