Re: spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-21 Thread Kris Kennaway
On Fri, Nov 21, 2003 at 01:08:13PM -0800, Nate Lawson wrote: > Since both of these happen in irq handlers, you might want to look at the > new random entropy gathering use of locking. I'm running a kernel with dev/random backed out to the day before mark's commits, because at the time I needed to

Re: spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-21 Thread Nate Lawson
Since both of these happen in irq handlers, you might want to look at the new random entropy gathering use of locking. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[E

Re: spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-21 Thread Kris Kennaway
0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = resume, IOPL = 0 > > current process = 40 (irq29: sym0) > > spin lock sched lock held by 0xc25a8640 for > 5 seconds > > panic: spin lock

Re: spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-20 Thread Craig Rodrigues
On Thu, Nov 20, 2003 at 03:17:29PM -0500, John Baldwin wrote: > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0x6300040 > > fault code= supervisor read, page not present > > instruction pointer = 0x8:0xc083611e > > Can you do

Re: spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-20 Thread John Baldwin
On 20-Nov-2003 Craig Rodrigues wrote: > On Thu, Nov 20, 2003 at 11:03:42AM -0800, Kris Kennaway wrote: >> c052e000 t propagate_priority >> c052e360 T init_turnstiles > > Is your crash similar to the one I saw on my system yesterday? No, your real panic was earlier. The pp was a later panic duri

Re: spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-20 Thread Craig Rodrigues
On Thu, Nov 20, 2003 at 11:03:42AM -0800, Kris Kennaway wrote: > c052e000 t propagate_priority > c052e360 T init_turnstiles Is your crash similar to the one I saw on my system yesterday? -- Craig Rodrigues http://crodrigues.org [EMAIL PROTECTED] Script started on Thu Nov 20 14:50:14 20

RE: spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-20 Thread John Baldwin
= resume, IOPL = 0 > current process = 40 (irq29: sym0) > spin lock sched lock held by 0xc25a8640 for > 5 seconds > panic: spin lock held too long > cpuid = 1; > Debugger("panic") > > Unfortunately it hangs there instead of breaking to DDB. > > The inst

spin lock sched lock held by 0xc25a8640 for > 5 seconds

2003-11-20 Thread Kris Kennaway
= 0x10:0xe00d2c3c frame pointer = 0x10:0xe00d2c64 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 40 (irq29: sym0) spin lock sched lock held by