From owner-freebsd-current@FreeBSD.ORG Tue Mar 25 10:32:41 2008 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 CEEEA106566C for ; Tue, 25 Mar 2008 10:32:41 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id 61CBD8FC22 for ; Tue, 25 Mar 2008 10:32:41 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.19] (helo=9.mx.freenet.de) by mout0.freenet.de with esmtpa (Exim 4.69) (envelope-from ) id 1Je6SN-0003NQ-G1 for current@freebsd.org; Tue, 25 Mar 2008 11:32:39 +0100 Received: from x0f75.x.pppool.de ([89.59.15.117]:27598 helo=peedub.jennejohn.org) by 9.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #12) id 1Je6SN-0001tt-7f for current@freebsd.org; Tue, 25 Mar 2008 11:32:39 +0100 Date: Tue, 25 Mar 2008 11:32:38 +0100 From: Gary Jennejohn To: current@freebsd.org Message-ID: <20080325113238.1371b173@peedub.jennejohn.org> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: bqlock.diff - wedges the box? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Mar 2008 10:32:41 -0000 I can't remember whether this patch was sent to -arch or -current, so I'm sending to -current. garyj:peedub:~:-bash:17> uname -a FreeBSD peedub.jennejohn.org 8.0-CURRENT FreeBSD 8.0-CURRENT #42: Fri Mar 21 16:08:49 CET 2008 garyj@peedub.jennejohn.org:/obj/usr/src/sys/amd64 amd64 I applied the bqlock.diff to my -current tree yesterday and booted the new kernel today. While browsing around with firefox the box wedged hard. Since I was in X I didn't see the error message. No crash dump was produced and I had to power-cycle the box to recover. Just thought I'd report my experience, even if it is only anecdotal. --- Gary Jennejohn