From owner-freebsd-current@FreeBSD.ORG Wed Jun 23 18:24:15 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E2EE106567D for ; Wed, 23 Jun 2010 18:24:15 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 77A988FC15 for ; Wed, 23 Jun 2010 18:24:15 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o5NINRmT019441; Wed, 23 Jun 2010 11:23:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=subject:from:reply-to:to:cc:in-reply-to:references: content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=xeMcWYH+ySXPrHHLAdpWJZcIJdfkp1FwfnvBTZxfgecPVh5hond/L/JY5BdDd6yB From: Sean Bruno To: Matthew Jacob In-Reply-To: <4C224BB1.8000104@feral.com> References: <1277315605.2478.22.camel@localhost.localdomain> <4C224BB1.8000104@feral.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 23 Jun 2010 11:23:26 -0700 Message-ID: <1277317406.2478.24.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" Subject: Re: Deadlock with kgmon -p X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 18:24:15 -0000 On Wed, 2010-06-23 at 13:00 -0500, Matthew Jacob wrote: > On 6/23/2010 10:53 AM, Sean Bruno wrote: > > Trying to track down a nasty with regard to Xen stuff and am now > > experiencing deadlocks on -current with a kernel configured with -g > > -ppp. > > > > The lockup will happen when I attempt to get the profiling data via > > kgmon -p. > > > > Not sure when this broke, but it's definitely broken in stable-7 as well > > as -current. Ideas? > > > > > > Dunno about anyone else's experience, but I can't get amd64 stable-7 > kernels on forward to even finish booting if built with config -pp. "config -p" *seems* to be ok at the moment on 7 and -Current Sean