From owner-freebsd-stable@FreeBSD.ORG Sun Feb 27 16:01:48 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC997106564A for ; Sun, 27 Feb 2011 16:01:48 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 9DB478FC08 for ; Sun, 27 Feb 2011 16:01:48 +0000 (UTC) Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta05.westchester.pa.mail.comcast.net with comcast id D3wT1g0071ZXKqc5541oVu; Sun, 27 Feb 2011 16:01:48 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta21.westchester.pa.mail.comcast.net with comcast id D41n1g00w0PUQVN3h41ofM; Sun, 27 Feb 2011 16:01:48 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 3DA6F9B427; Sun, 27 Feb 2011 08:01:46 -0800 (PST) Date: Sun, 27 Feb 2011 08:01:46 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20110227160145.GA1885@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: ath(4) panic + stuck beacon issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2011 16:01:49 -0000 I have a crash report to provide (for RELENG_8 dated 2010/02/12), but I'd like to know who's maintaining ath(4) at this point in time. I also need to discuss a commonly-reported issue with AR5416 and/or AR9280 cards (e.g. D-Link DWA-552 running in 802.11g mode w/ WEP) spitting out "stuck beacon" errors, which are what I was trying to resolve when the kernel crashed. (I induced the crash, but I'm not sure exactly why/how). Given that the issue has existed for years now... http://www.daemonforums.org/showthread.php?t=3388 http://forums.freebsd.org/showthread.php?t=5983 http://forum.pfsense.org/index.php?topic=21374.0 http://forum.pfsense.org/index.php?topic=32041.0 http://www.broadbandreports.com/forum/r25070916-FreeBSD-MIPS-dev-Adrian-Chad-on-stuck-beacon-issue http://forums.freebsd.org/showthread.php?t=22112 (recent & thorough!) ...and "bintval 1000" does not solve it, let's work together to find a solution. If you need hardware I will be more than happy to buy you (brand new) cards which you can keep. If you have beta/test drivers and/or can provide *thorough* debugging instructions, I will be more than happy to do what I can. I'll also point out the Linux madwifi folks have an *entire page* dedicated to this problem, which is quite interesting: http://madwifi-project.org/wiki/StuckBeacon If a workaround or solution isn't plausible, what cards do people actually recommend that work reliably / have reliable drivers? I was under the impression Atheros cards were reliable/decent compared to, say, Broadcom. Is iwn(4) reliable? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |