Date: Wed, 23 Jun 2010 11:23:26 -0700 From: Sean Bruno <seanbru@yahoo-inc.com> To: Matthew Jacob <mj@feral.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Deadlock with kgmon -p Message-ID: <1277317406.2478.24.camel@localhost.localdomain> In-Reply-To: <4C224BB1.8000104@feral.com> References: <1277315605.2478.22.camel@localhost.localdomain> <4C224BB1.8000104@feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1277317406.2478.24.camel>