From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 27 18:05:13 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 830EB106566C for ; Tue, 27 Dec 2011 18:05:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3CB568FC13 for ; Tue, 27 Dec 2011 18:05:12 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so16156518vcb.13 for ; Tue, 27 Dec 2011 10:05:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=axWylnr69hW0F3NvdA4iw1AOtpicJVoGMDqvXiRA/Hw=; b=fmH0H365Vc30ttO5if+QWpvtgUeMOVmBbw1KibSW9gP3iYrPePbMqHt1ycg7sCYWLn 99ogoD8D8gs4UxwtwTi4eQKUF/ndhC3TD4LsE4Pp1GsVHwzHd6LdJ5CKkTsG2q0/LwLV RRHnSqaa8zdy8iZXUYrDx+97AqRyBSxBqsdwc= MIME-Version: 1.0 Received: by 10.220.153.134 with SMTP id k6mr16891944vcw.23.1325009112499; Tue, 27 Dec 2011 10:05:12 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Tue, 27 Dec 2011 10:05:12 -0800 (PST) In-Reply-To: <4EFA0539.2020508@bettercom.de> References: <4EF50AF4.3030105@bettercom.de> <4EFA0539.2020508@bettercom.de> Date: Tue, 27 Dec 2011 10:05:12 -0800 X-Google-Sender-Auth: AgJ_fz3wwBf52J069wxxhhzaaQg Message-ID: From: Adrian Chadd To: Martin Lesser Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath updates - please test 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: Tue, 27 Dec 2011 18:05:13 -0000 On 27 December 2011 09:49, Martin Lesser wrote: > Unfortunately the "stuck beacons" appeared again - not as much as in STABLE > in the past but probably too much to ignore: > > Dec 25 10:20:18 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) > Dec 25 10:20:27 fs last message repeated 29 times > Dec 25 10:20:27 fs kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing > Dec 25 10:20:40 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) > Dec 25 10:20:51 fs last message repeated 36 times > Dec 25 10:20:51 fs kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing Yup. :( > I've set hw.ath.debug=2147483647 but I'm not sure whether that makes sense. > Which debug-infos can I provide to help to get this bug out of the way? Are > there plans to backport the actual /ath back to CURRENT? "Actual ath" ? What do you mean? :) > > Additionally I ordered a D-Link DWA-547 [1] and hope not only to get rid of > these stuck beacons but also to test 11n a little bit more. Hi, That's likely a bit much. Also, the AR5416 isn't all that great a NIC, it's their first generation 11n NIC. The newer stuff is a _lot_ nicer. So anything with an AR9220/AR9280 or AR9227/AR9287 (PCI/PCIe) would be better. That said, unless I find a mine of useful information about the older pre-11n NICs, it's unlikely I'll find time/resources to track down and fix bugs. The only thing I can think of is "overly noisy environment." I need to write up some tools to make that easier to ascertain. Stay tuned. Thanks, Adrian