Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2003-09-18 Thread Daniel Eischen
On Thu, 18 Sep 2003, Brad Knowles wrote: > At 4:47 PM -0700 2003/09/17, Doug White wrote: > > > This came up at the developer summit. We do need to upgrade/make > > significant changes to gdb for it to understand threaded debugging. The > > panics might be interesting as it might be tickling

Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2003-09-18 Thread Brad Knowles
At 4:47 PM -0700 2003/09/17, Doug White wrote: This came up at the developer summit. We do need to upgrade/make significant changes to gdb for it to understand threaded debugging. The panics might be interesting as it might be tickling other issues, but before we can really debug threaded ap

Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2003-09-17 Thread Doug White
On Tue, 16 Sep 2003, Morten Rodal wrote: > So this brings up the question, is there a known problem with > debugging multi-threaded applications (which use libkse) that can > cause a panic? I will bring home my laptop, and will be able to use a > serial debugger if that would help anyone willing

Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2003-09-15 Thread Morten Rodal
w copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled panic messages: ---

panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2003-09-11 Thread Morten Rodal
rmydesk-freebsd"... panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled panic messages: --- panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled cpuid = 1; lapic.id = Stack backtrace: boot() called on cpu#1 syncing disks, buffers remaini

Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2002-07-15 Thread Andrew Gallatin
Peter Wemm writes: > Eww! Care to confirm that the following works? I was going to just commit > it since it is pretty obvious, but a brief sanity check would probably > be an idea. (beware, xterm cut/paste whitespace damage). > > ddb runs with interrupts disabled and the other cpus halt

Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2002-07-15 Thread Peter Wemm
device 1.0 on pci1 > > Debugger("here") # breakpoint I put in my module's load path > > Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 > db> break generic_bzero > db> c > panic: absolutely cannot call smp_ipi_shootdown with interrupts > alre

panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled

2002-07-15 Thread Andrew Gallatin
eak generic_bzero db> c panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled cpuid = 1; lapic.id = 0100 boot() called on cpu#1 syncing disks... panic: bremfree: bp 0xce67d2b4 not locked cpuid = 1; lapic.id = 0100 boot() called on cpu#1 Uptime: 2m9s Dumping 511