From owner-freebsd-wireless@FreeBSD.ORG  Tue Jan 17 19:00:30 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 9D19F106564A
	for <freebsd-wireless@hub.freebsd.org>;
	Tue, 17 Jan 2012 19:00:30 +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 8CC178FC1E
	for <freebsd-wireless@hub.freebsd.org>;
	Tue, 17 Jan 2012 19:00:30 +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 q0HJ0Uou064732
	for <freebsd-wireless@freefall.freebsd.org>;
	Tue, 17 Jan 2012 19:00:30 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0HJ0Urr064730;
	Tue, 17 Jan 2012 19:00:30 GMT (envelope-from gnats)
Date: Tue, 17 Jan 2012 19:00:30 GMT
Message-Id: <201201171900.q0HJ0Urr064730@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 19:00:30 -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 19:50:57 +0100

 On 15-01-2012 12:10, Adrian Chadd wrote:
 > Hi,
 > 
 > So I want to establish whether the scan logic has hung, or whether the
 > scan logic has completed but left the interface hung.
 > 
 > How's your C? Would you mind doing some quick hacking:
 > 
 > * add a new variable in struct ath_softc, call it "sc_in_scan";
 > * set it to 1 in ath_scan_start (don't add any locks)
 > * set it to 0 in ath_scan_end (don't add any locks)
 > * edit the 'txagg' sysctl code in if_ath_sysctl.c to print out the
 > value of sc_in_scan;
 > 
 > 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.
 
 ...or was I supposed to _only_ do ifconfig wlan0 scan once the interface has
 died?
 
 -- 
 Joel