From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 11 20:10:15 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 6C5B7106564A for ; Sun, 11 Mar 2012 20:10:15 +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 573C98FC14 for ; Sun, 11 Mar 2012 20:10:15 +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 q2BKAFkO000570 for ; Sun, 11 Mar 2012 20:10:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2BKAF9U000569; Sun, 11 Mar 2012 20:10:15 GMT (envelope-from gnats) Date: Sun, 11 Mar 2012 20:10:15 GMT Message-Id: <201203112010.q2BKAF9U000569@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:10:15 -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:01:00 +0100 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. So I've been doing a binary search in order to nail the specific revision that fixed my issues with ath. The problem usually occur after 6-8 hours of uptime, but sometimes 30 minutes is enough. I've tested each revision twice. If it survived 12 hours of uptime, I rebooted the machine and let it run for another 12 hours just to be sure that each the revision really was OK. Same goes for revisions that dies - each time ath died I rebooted the machine in order to be sure that I could reproduce the problem again. 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? -- Joel