From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 11 00:00:55 2012 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 6D409106566C for ; Sun, 11 Mar 2012 00:00:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3B0388FC08 for ; Sun, 11 Mar 2012 00:00:54 +0000 (UTC) Received: by dald2 with SMTP id d2so3602813dal.13 for ; Sat, 10 Mar 2012 16:00: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Fld0UW750MwC1w871CU+PyhfnrZUo+ICu6M5uXcM0Og=; b=azIO0AFNfwezzm1jPm9DIrkHtogR0lRLGROowrhEHtHkfE71K1lAY5qVknOt7aIOs6 gxZc0+LyGPckpLLOCF3Y9IeAHuJ5WW8ZtAh+NPNOQfVqMRl1r7G2LFeNYb03kymU60di vILE6zKtlcqEF3vFUW0a1EbdiY0K4TV1NY+ioSzvqQOWlGlRW4YNcWz6FCEqM+EmmiW9 s3iYzaVf1Nb4c6yZK94R+IoE6/yIhYboUfLQlEqjPsCJOAiF3uMFWQSCxfVI771VoSPg lXeQtjQgc3qblqJIqKighBpn3+VZIsccyat783DWhJyHa3cSz2MBSGAvqVDcP7oMQ6Ut RXJw== MIME-Version: 1.0 Received: by 10.68.240.135 with SMTP id wa7mr11863542pbc.7.1331424054823; Sat, 10 Mar 2012 16:00:54 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.143.33.5 with HTTP; Sat, 10 Mar 2012 16:00:54 -0800 (PST) In-Reply-To: <4F5BDF3C.8070605@unsane.co.uk> References: <4F59DD98.8080905@unsane.co.uk> <4F5AA149.8000904@unsane.co.uk> <4F5BDF3C.8070605@unsane.co.uk> Date: Sat, 10 Mar 2012 16:00:54 -0800 X-Google-Sender-Auth: r7XfDiFCHNtjDlmdZXbi8aTujkY Message-ID: From: Adrian Chadd To: Vincent Hoffman Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: (more) bugs fixed in -HEAD, AP mode is now mostly (again) stable! 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: Sun, 11 Mar 2012 00:00:55 -0000 On 10 March 2012 15:09, Vincent Hoffman wrote: > Ok now I'm past the panic commit, it ran fine for about 1/2 hour then I got > Mar 10 22:37:30 ostracod kernel: ath0: device timeout > and nothing more, which was unexpected. Right. Well, "device timeout" can occur for a lot of reasons. The reason it occurs is that a TX was scheduled but the TX completion doesn't come in, so the watchdog countdown fires. The cause can sometimes be because of an actual TX stall, but these days it's almost certainly a corner case during background scanning and/or some vap state transition. I know of at least one case where it's due to scan (where it does something odd - it transitions to scan, sends out a frame, then cancels interrupts so it can't receive the TX completion; no subsequent TX completion occurs within 5 seconds. So it's not REALLY a timeout, it's just bad packet handling.) I'll let the list know when I've fixed that. For now, please disable bgscan (ifconfig wlan0 -bgscan.) > I have > options ATH_ENABLE_11N > options AH_DEBUG > options ATH_DEBUG > options ATH_DIAGAPI > > in my kernel config. > > I've reverted to a working 11G version for now as my wife is watching > bbc iplayer on a tv connected via that machine at the moment ;) > If you have anything you would like me to try let me know and i'll try > it once shes's done. Is this in access point mode, or in station mode? > message log from boot till the timeout (then me rebooting) at > http://unsane.co.uk/message-ath-timeout.txt The next time it happens, please do this: sysctl dev.ath.0.txagg=1 and then check dmesg, email the list the output. I'd like to see if the TX queue is stuck. Then, force a scan: ifconfig wlan0 scan Even if it's in hostap mode, it'll cause a full TX queue flush and if 11n TX aggregation is stuck for whatever reason, it'll complain bitterly at you in dmesg. Thanks, Adrian