Date: Thu, 10 May 2007 21:19:29 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Scott Swanson <scotts@inetz.com> Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: panic: spin lock held too long (w/ backtrace) Message-ID: <20070511011929.GA76360@xor.obsecurity.org> In-Reply-To: <4643C34F.9070504@inetz.com> References: <46438569.1000506@inetz.com> <20070510214348.GA68925@xor.obsecurity.org> <4643C010.7060302@inetz.com> <20070511010654.GA75689@xor.obsecurity.org> <4643C34F.9070504@inetz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 10, 2007 at 07:13:51PM -0600, Scott Swanson wrote: > Kris Kennaway wrote: > > On Thu, May 10, 2007 at 07:00:00PM -0600, Scott Swanson wrote: > > > >>>> Unread portion of the kernel message buffer: > >>>> spin lock smp rendezvous held by 0xc95a5900 for > 5 seconds > >>> What is thread 0xc95a5900 doing? > >>> > >>> Kris > >>> > >> Is this the best way to determine the action of the thread? > >> > >> Regards; > >> Scott > >> > >> (kgdb) info threads > >> 90 Thread 100123 (PID=18303: bsdtar) 0xc0644f5b in sched_switch > >> (td=0xc95a5900, newtd=0xc92aad80, flags=0) at > >> /usr/src/sys/kern/sched_4bsd.c:973 > > > > Yes, now 'proc 18303' and 'bt'. > > > > Kris > > > (kgdb) proc 18303 > (kgdb) bt > #0 0xc0644f5b in sched_switch (td=0xc95a5900, newtd=0xc92aad80, > flags=0) at /usr/src/sys/kern/sched_4bsd.c:973 > #1 0xeaa6dcb4 in ?? () > #2 0x00000001 in ?? () > #3 0x0ee2c000 in ?? () > #4 0x00000000 in ?? () > #5 0x00004000 in ?? () > #6 0x00000000 in ?? () > #7 0x00000000 in ?? () > #8 0xc95a5900 in ?? () > #9 0xeaa6dd30 in ?? () > #10 0xc081a8fb in syscall (frame=Cannot access memory at address 0x4008 > ) at /usr/src/sys/i386/i386/trap.c:983 > Previous frame inner to this frame (corrupt stack?) Garbage :( Are you using any modules? Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070511011929.GA76360>