From owner-p4-projects@FreeBSD.ORG Fri Jun 24 19:33:14 2005 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 7D4DD16A420; Fri, 24 Jun 2005 19:33:13 +0000 (GMT) X-Original-To: perforce@FreeBSD.org Delivered-To: perforce@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50F1616A41C; Fri, 24 Jun 2005 19:33:13 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2567C43D1D; Fri, 24 Jun 2005 19:33:13 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 6865346B80; Fri, 24 Jun 2005 15:33:12 -0400 (EDT) Date: Fri, 24 Jun 2005 20:36:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Wemm In-Reply-To: <200506231604.23036.peter@wemm.org> Message-ID: <20050624203602.M42596@fledge.watson.org> References: <200506222312.j5MNChMh079831@repoman.freebsd.org> <200506231444.08027.jhb@FreeBSD.org> <200506231604.23036.peter@wemm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Perforce Change Reviews , Peter Wemm , John Baldwin Subject: Re: PERFORCE change 78828 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2005 19:33:14 -0000 On Thu, 23 Jun 2005, Peter Wemm wrote: > On Thursday 23 June 2005 11:44 am, John Baldwin wrote: >> On Wednesday 22 June 2005 07:12 pm, Peter Wemm wrote: >>> http://perforce.freebsd.org/chv.cgi?CH=78828 >>> >>> Change 78828 by peter@peter_melody on 2005/06/22 23:12:33 >>> >>> Freeze things for the dump snapshot. >> >> This may be a bad idea since we may panic with sched_lock held and it >> would be very nice to get a dump there and not just deadlock. > > Yeah. I'm really not sure what to do though because with interrupts > still happening, it upsets some of the driver dump routines. eg: when > you call this from ddb. Aren't we supposed to be running with interrupts disabled, and having IPI'd the other processors to stop (along with a barrier to make sure they did), and operating entirely polled? Robert N M Watson