From owner-freebsd-current@FreeBSD.ORG Sat Oct 1 12:46:56 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CB941065670; Sat, 1 Oct 2011 12:46:56 +0000 (UTC) (envelope-from joel@vnode.se) Received: from mail.vnode.se (mail.vnode.se [62.119.52.80]) by mx1.freebsd.org (Postfix) with ESMTP id C6E7D8FC13; Sat, 1 Oct 2011 12:46:55 +0000 (UTC) Received: from mail.vnode.se (localhost [127.0.0.1]) by mail.vnode.se (Postfix) with ESMTP id 2970BE3F07A; Sat, 1 Oct 2011 14:46:54 +0200 (CEST) X-Virus-Scanned: amavisd-new at vnode.se Received: from mail.vnode.se ([127.0.0.1]) by mail.vnode.se (mail.vnode.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gf3Qf8gE6WjY; Sat, 1 Oct 2011 14:46:52 +0200 (CEST) Received: from goofy03.vnode.local (wg.benders.se [212.247.52.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.vnode.se (Postfix) with ESMTPSA id C3861E3F079; Sat, 1 Oct 2011 14:46:51 +0200 (CEST) Date: Sat, 1 Oct 2011 14:46:50 +0200 From: Joel Dahl To: Adrian Chadd Message-ID: <20111001124649.GB56117@goofy03.vnode.local> References: <09C13664-4FC0-41F3-8849-CE875B3A6CC0@vnode.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org Subject: Re: BETA2 panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2011 12:46:56 -0000 On 30-09-2011 17:52, Adrian Chadd wrote: > Hi, > > Would you please try this patch? Make sure that witness and the rest > of the lock debugging is enabled. > > I've been working on this problem with someone else on the list (but I > can't trigger it myself; I think I need to get some dual-CPU wireless > test hardware.) My laptop has been running with your patch for almost 8 hours now. No panics. -- Joel