Date: Wed, 9 Feb 2005 20:37:10 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Eric Anderson <anderson@centtech.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Panic - FFS background buffer bla bla Message-ID: <20050210043710.GA26601@xor.obsecurity.org> In-Reply-To: <420AE1E1.5030403@centtech.com> References: <420ADAFC.40504@centtech.com> <20050210040102.GA11457@xor.obsecurity.org> <420ADEF7.30003@centtech.com> <20050210042321.GA26438@xor.obsecurity.org> <420AE1E1.5030403@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Wed, Feb 09, 2005 at 10:24:01PM -0600, Eric Anderson wrote: > Kris Kennaway wrote: > > >On Wed, Feb 09, 2005 at 10:11:35PM -0600, Eric Anderson wrote: > > > > > > > >>After rebooting (with a console plugged in), I get this: > >>Fast boot: skipping disk checks. > >>panic: panic: thread 100079(cp):2 holds Giant but isn't blocked on a lock > >> > >>cpuid = 0 > >>KDB: enter: panic > >>[thread pid 27 tid 100001 ] > >>Stopped at kdb_enter+0x30: leave > >> > >>Backtrace: > >> > [..snip..] > > >> > >>Hope that helps.. Anything else I can give you? > >> > >> > > > >That's actually not the real panic. Look at the backtraces of other > >processes to find the first panic. If you can examine the core in gdb > >to obtain source code line numbers, that would help too. > > > > > > Oh.. Ok, well, how do I find the real panic? I can do any debugging > needed - but I'm not sure what to do here as far as examining the core > in gdb.. I already said..look at the backtraces of the other processes. You'll find another one that has panicked. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCCuT2Wry0BWjoQKURAgQMAJ9Pdeq/SY0VmmRxmcjETtDbQk6lKwCgqPLM T4rtqDxVY831XKJHT6z36eE= =V5tl -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050210043710.GA26601>