From owner-freebsd-current Thu Mar 6 10:57: 6 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D5B937B401 for ; Thu, 6 Mar 2003 10:57:05 -0800 (PST) Received: from smtp.netcologne.de (smtp.netcologne.de [194.8.194.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA2FC43F93 for ; Thu, 6 Mar 2003 10:57:04 -0800 (PST) (envelope-from tmseck-usenet@netcologne.de) Received: from localhost (xdsl-213-196-208-177.netcologne.de [213.196.208.177]) by smtp.netcologne.de (Postfix) with ESMTP id B9F9686731 for ; Thu, 6 Mar 2003 19:56:59 +0100 (MET) Received: (qmail 1089 invoked by uid 1001); 6 Mar 2003 18:57:09 -0000 Date: 6 Mar 2003 18:57:09 -0000 Message-ID: <20030306185709.1088.qmail@laurel.tmseck.homedns.org> From: Thomas Seck To: freebsd-current@freebsd.org Subject: Re: "blockable sleep lock" panic in latest -current. Organization: private site In-Reply-To: <20030307035011.I2362-100000@gamplex.bde.org> X-Attribution: tms Mail-Copies-To: nobody Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Bruce Evans (bde@zeta.org.au): > This is the usual panic from sync() in panic() tripping over a lock. > Calling sync() in panic was never safe and now usually fails. Should one set "kern.sync_on_panic" to zero then? --Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message