Re: panic: spin lock held too long (w/ backtrace)

2007-05-11 Thread Scott Swanson
[EMAIL PROTECTED] /usr/src/sys/i386/conf kldstat Id Refs AddressSize Name 13 0xc040 65e308 kernel 21 0xc0a5f000 59f20acpi.ko So, yes then :) Can you follow the steps for debugging modules and see if it gives a better trace? Kris Unfortunately, after

Re: panic: spin lock held too long (w/ backtrace)

2007-05-11 Thread Kris Kennaway
On Fri, May 11, 2007 at 10:43:54AM -0600, Scott Swanson wrote: [EMAIL PROTECTED] /usr/src/sys/i386/conf kldstat Id Refs AddressSize Name 13 0xc040 65e308 kernel 21 0xc0a5f000 59f20acpi.ko So, yes then :) Can you follow the steps for debugging modules and

panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Scott Swanson
Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have been able to re-create the problem fairly consistently just by looping a script that tars

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Kris Kennaway
On Thu, May 10, 2007 at 02:49:45PM -0600, Scott Swanson wrote: Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have been able to

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Scott Swanson
Kris Kennaway wrote: On Thu, May 10, 2007 at 02:49:45PM -0600, Scott Swanson wrote: Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Scott Swanson
Kris Kennaway wrote: On Thu, May 10, 2007 at 02:49:45PM -0600, Scott Swanson wrote: Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Kris Kennaway
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;

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Scott Swanson
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?

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Kris Kennaway
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?

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Scott Swanson
(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 0x0001 in ?? () #3 0x0ee2c000 in ?? () #4 0x in ?? () #5 0x4000 in ?? () #6 0x in ?? () #7

Re: panic: spin lock held too long (w/ backtrace)

2007-05-10 Thread Kris Kennaway
On Thu, May 10, 2007 at 07:44:37PM -0600, Scott Swanson wrote: (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 0x0001 in ?? () #3 0x0ee2c000 in ?? () #4