From owner-freebsd-wireless@FreeBSD.ORG Tue Nov 22 02:28:05 2011 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 450D81065673; Tue, 22 Nov 2011 02:28:05 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id F14C68FC12; Tue, 22 Nov 2011 02:28:04 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id pAM2S4vC052640; Mon, 21 Nov 2011 19:28:04 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id pAM2S49w052637; Mon, 21 Nov 2011 19:28:04 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 21 Nov 2011 19:28:04 -0700 (MST) From: Warren Block To: Alexander Best In-Reply-To: <20111121225343.GA19155@freebsd.org> Message-ID: References: <20111121131730.GA3599@freebsd.org> <20111121152054.GA22220@freebsd.org> <20111121221224.GA11508@freebsd.org> <20111121225343.GA19155@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Mon, 21 Nov 2011 19:28:04 -0700 (MST) Cc: Adrian Chadd , freebsd-wireless@FreeBSD.ORG Subject: Re: issues with the recent ath commits (r227740, r227651, ...) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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: Tue, 22 Nov 2011 02:28:05 -0000 On Mon, 21 Nov 2011, Alexander Best wrote: > On Mon Nov 21 11, Alexander Best wrote: >> On Tue Nov 22 11, Adrian Chadd wrote: >>> Hi, >>> >>> Please try this patch: >> >> looking very promising so far. haven't got the boot-up-panic. i'll let my >> system run for a few hours, to see, if the lock up has also been resolved. > > ok. after > 45 minutes uptime i can confirm that the patch fixes the issues i > experienced beforehand. unless i didn't get a boot-up-panic, my system locked > up after < 5 minutes. Likewise here, the patch works fine.