From owner-freebsd-stable@FreeBSD.ORG Wed Jun 14 00:34:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B406916A47D for ; Wed, 14 Jun 2006 00:34:54 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 682D443D46 for ; Wed, 14 Jun 2006 00:34:54 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.169] ([10.0.0.169]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k5E0YrEf012282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jun 2006 17:34:54 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <448F59EE.9030801@errno.com> Date: Tue, 13 Jun 2006 17:35:58 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5 (X11/20060209) MIME-Version: 1.0 To: Alex Burke References: <448F36CB.6000604@cs.okstate.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD STABLE Subject: Re: atheros 'device timeout' 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: Wed, 14 Jun 2006 00:34:54 -0000 Alex Burke wrote: > Hi, > > Just to chime in and say that I have seen device timeout messages too > - the behaviour for me was (ok, maybe a bit random but...) having > mounted an NFS exported /usr/src and hammering it with a buildworld. > So really, I guess I can only say that I have seen this when the > wireless card was under some very heavy load. > > Symptoms where I would notice things just stop, it dissociates...and > sure enough, on the console was an ath0: device timeout message. I was > using WPA2-PSK, and the card I have is a Netgear WPN511 (Cardbus), > which i think defines itself as a 5212 chip. I was running FreeBSD 6.0 > with all security patches at the time. > > Anyways, it does appear that it can happen, and glad I am not the only > one hititng it - would be interested to find out how hard you were > working it when it occured though. > > If anoybody needs any furhter information, I will put 6.1 on my laptop > and see if I can reproduce and/or retrieve anything that may help. You are operating in station mode; the original poster reported an issue when operating in ap mode. I believe problems of the sort you report have been resolved in 6.1 or at the very least they are an annoyance and do not significantly disturb operation. Sam