From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 11 20:20:12 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 32025106566B for ; Sun, 11 Mar 2012 20:20:12 +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 1DA8B8FC17 for ; Sun, 11 Mar 2012 20:20:12 +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 q2BKKB3o010769 for ; Sun, 11 Mar 2012 20:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2BKKBIF010768; Sun, 11 Mar 2012 20:20:11 GMT (envelope-from gnats) Date: Sun, 11 Mar 2012 20:20:11 GMT Message-Id: <201203112020.q2BKKBIF010768@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Joel Dahl 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 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 20:20:12 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl To: Adrian Chadd Cc: bug-followup@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sun, 11 Mar 2012 21:13:46 +0100 On 11-03-2012 13:07, Adrian Chadd wrote: > Hi! > > On 11 March 2012 13:01, Joel Dahl wrote: > > Some news... > > > > I updated from a Jan 18 CURRENT to a Feb 19 CURRENT some time ago and the > > issue was gone. Adrian asked me to try to track down the revision that fixed > > the problem, and that's what I've been doing for the last two weeks. > > Sweet! > > > > Revision 231852 does not survive for very long. It dies as usual. I haven't > > been able to make any revision before 231852 survive longer than 8 hours. > > > > Revision 231854 has survived my 12 hour testing period 3 times and I haven't > > been able to crash any revision after 231854. > > > > Adrian, your commit to the ath driver (231854) seems to fix my ath problems. > > Does that make sense to you? > > Nope. That just started shifting around locks. Can you please try > 231852 with the debugging patch I threw you (that patched > ieee80211_scan.c) and see if it complains? Sure, I'll try 231852 + your patch. > If that patch fixed anything, it just delayed things enough to hide > what's going on... I see. Hiding a problem is not equal to fixing it. :-) -- Joel