Date: Fri, 21 Aug 2009 02:10:02 -0700 From: Pramod Srinivasan <pramod@juniper.net> To: John Baldwin <jhb@freebsd.org>, "freebsd-smp@freebsd.org" <freebsd-smp@freebsd.org> Subject: Re: LOCK_PROFILING Message-ID: <C6B3B27A.15FB1%Pramod@juniper.net> In-Reply-To: <200908190757.01982.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi John, On 8/19/09 4:57 AM, "John Baldwin" <jhb@freebsd.org> wrote: >=20 > It sounds like a tripe fault. I suspect you are recursing on your stack > somehow leading to a double fault that faults again trying to get a lock = to > output to the console perhaps (that would explain the lack of double faul= t > messages if that were the case). Perhaps a lock used in the profiling is > incorrectly being profiled? Yes, this is right!! The clock_lock was not initialized with MTX_NOPROFILE, and we ended up profiling the clock_lock recursively until we overflowed the stack. Thanks for pointing out. Thanks, Pramod
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C6B3B27A.15FB1%Pramod>