From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 00:00:44 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 86704F59 for ; Sat, 12 Jan 2013 00:00:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by mx1.freebsd.org (Postfix) with ESMTP id 26422A76 for ; Sat, 12 Jan 2013 00:00:43 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id 15so1128082wgd.16 for ; Fri, 11 Jan 2013 16:00:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UZMYLWtg45XCK72IjJBsFQ+nYhUNv0GxBmTrCaYyP7U=; b=PAHrR1ixt/ss64ibeYQhhXv5TMN7MQGb9ee3bimX5nseYvgJNP+qEneMaDEElbx1dC sYGGDEPLMDBtX4naKHNYbyLp8LqinA9fDa5qL29aMrzgJJWbYyDVhZcWRAOOqVM+KfSC tYCRb1m9Z+V9BuIZ4ypiB8nsJYZKvtDD6KB5MyD0/8L2mRDmA8Gg/vzns8TVJ4KTH4bC K1AT5tg5NMPsu7kJHk/Y+8W9EuKWTdvrysNQIcaDhIQG931Jpa7Vlya4mX7FxJLzXJ8e g5EBAjjW+CDFOeU9wdfptTCzIRADxcROrz7fmCCL0zQsDOT7d/wUWu0COlMm+SScHVYN Mfog== MIME-Version: 1.0 X-Received: by 10.180.33.44 with SMTP id o12mr1472946wii.28.1357948836917; Fri, 11 Jan 2013 16:00:36 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 11 Jan 2013 16:00:36 -0800 (PST) In-Reply-To: References: Date: Fri, 11 Jan 2013 16:00:36 -0800 X-Google-Sender-Auth: DuHA-UK_Lt6xYeuz9BDvxDtYKcc Message-ID: Subject: Re: Debugging Stalls with ath(4) From: Adrian Chadd To: Andrew Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 12 Jan 2013 00:00:44 -0000 .. ok, so reading about this a bit more. Going in and out of power save state could be it. Having it wait for a second is possible when you're in power save, because it's quite possible that the device is _in_ power save state for that long. Enable power state debugging in net80211 and see what's happening. You'll see it come in and out of power save, as well as it queuing up frames (and if the node power save queue overflows.) It'll also log whether it receives ps-poll frames (which I know handling of is broken in various ways in -HEAD and will be for a few more weeks) or whether it's just coming in and out of power save frames. Thanks, Adrian