From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 25 23:30:16 2012 Return-Path: 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 61B4D1065670 for ; Sat, 25 Feb 2012 23:30:16 +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 4D4EC8FC08 for ; Sat, 25 Feb 2012 23:30:16 +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 q1PNUGSb034560 for ; Sat, 25 Feb 2012 23:30:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1PNUGNd034557; Sat, 25 Feb 2012 23:30:16 GMT (envelope-from gnats) Date: Sat, 25 Feb 2012 23:30:16 GMT Message-Id: <201202252330.q1PNUGNd034557@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Adrian Chadd 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: Adrian Chadd 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, 25 Feb 2012 23:30:16 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Adrian Chadd To: Joel Dahl Cc: bug-followup@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sat, 25 Feb 2012 15:22:49 -0800 Hi Joel, I've been exploring this a little further. I wonder if the actual bg scan task is stuck - even though scan start/end is being called correctly inside scan_task(), I wonder if something is trampling over the flags at the same time and causing scan_task() to think another scan is coming, but never does. A bgscan should be occuring every X seconds though. So I wonder why it wouldn't next be running. So would you mind plugging it back in and having it fail, then once it does: wlandebug +power +scan And then let's see if it actually _does_ try to do background scanning once it's hung. I hope it prints something useful about why it isn't running. Thanks, adrian