From owner-freebsd-wireless@FreeBSD.ORG  Tue Jan 17 21:00:33 2012
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 141D9106572F
	for <freebsd-wireless@hub.freebsd.org>;
	Tue, 17 Jan 2012 21:00:33 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 02D7C8FC18
	for <freebsd-wireless@hub.freebsd.org>;
	Tue, 17 Jan 2012 21:00:33 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0HL0WMX076522
	for <freebsd-wireless@freefall.freebsd.org>;
	Tue, 17 Jan 2012 21:00:32 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0HL0WVW076521;
	Tue, 17 Jan 2012 21:00:32 GMT (envelope-from gnats)
Date: Tue, 17 Jan 2012 21:00:32 GMT
Message-Id: <201201172100.q0HL0WVW076521@freefall.freebsd.org>
To: freebsd-wireless@FreeBSD.org
From: Joel Dahl <joel@freebsd.org>
Cc: 
Subject: Re: kern/163318: [ath] ath(4) stops working
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Joel Dahl <joel@freebsd.org>
List-Id: "Discussions of 802.11 stack,
	tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 21:00:33 -0000

The following reply was made to PR kern/163318; it has been noted by GNATS.

From: Joel Dahl <joel@freebsd.org>
To: Adrian Chadd <adrian.chadd@gmail.com>
Cc: bug-followup@freebsd.org
Subject: Re: kern/163318: [ath] ath(4) stops working
Date: Tue, 17 Jan 2012 21:56:16 +0100

 On 17-01-2012 10:53, Adrian Chadd wrote:
 > On 17 January 2012 10:50, Joel Dahl <joel@freebsd.org> wrote:
 > >> Then verify that it's working as advertised:
 > >>
 > >> * sysctl dev.ath.0.txagg=1 and check dmesg - sc_in_scan should be 0;
 > >> * do a manual scan (ifconfig wlan0 scan) and then redo the above
 > >> sysctl - it should be 1.
 > >
 > > Hm. I did the above changes and rebuilt my kernel. If I do sysctl
 > > dev.ath0.txagg=1, sc_in_scan is 0 just as expected. If I do a manual scan
 > > right after, it is still set to 0.
 > 
 > right. Can you check the sc_in_scan value _during_ an ifconfig wlan0
 > scan ? (ie, whilst it's running.)
 > 
 > You'll have to be ninja-fast.
 > 
 > I just want to verify that it's actually working..
 
 Yes, it's set to 1 for a very short period during the scan. So it seems to
 work like it should.
 
 > > ...or was I supposed to _only_ do ifconfig wlan0 scan once the interface has
 > > died?
 > 
 > The above is just to verify that it's working. Once that's done, check
 > sc_in_scan once the interface has hung.
 > 
 > I'm testing the hypothesis that the scan logic is "hung" somehow and
 > that is why the interface never comes out of STA power save mode.
 
 I'll check this next.
 
 -- 
 Joel