On Fri, 6 Jun 2003, John Baldwin wrote:
> On 06-Jun-2003 David P. Reese Jr. wrote:
> > I've been getting a lot of these for the last two weeks on my SMP box.
> > This panic is on -CURRENT from earlier today. Scheduler is ULE.
> >
> > lock order reversal
> > 1st 0xc047f820 sched lock (sched lock
Hm... Getting a core wont be that easy. After the previously mentionsed
sched_choose() panic:
db> call doadump
Dumping 383 MB
ata0: resetting devices ..
panic: blockable sleep lock (sleep mutex) PCPU 512 @ /usr/src/sys/vm/uma_core.c:1343
cpuid = 0; lapic.id =
Debugger("panic")
Fatal t
On Fri, Jun 06, 2003 at 12:39:46PM -0400, John Baldwin wrote:
>
> On 06-Jun-2003 David P. Reese Jr. wrote:
> > I've been getting a lot of these for the last two weeks on my SMP box.
> > This panic is on -CURRENT from earlier today. Scheduler is ULE.
> >
> > lock order reversal
> > 1st 0xc047f8
On 06-Jun-2003 David P. Reese Jr. wrote:
> I've been getting a lot of these for the last two weeks on my SMP box.
> This panic is on -CURRENT from earlier today. Scheduler is ULE.
>
> lock order reversal
> 1st 0xc047f820 sched lock (sched lock) @ /usr/src/sys/kern/kern_intr.c:548
> 2nd 0xc04b
I've been getting a lot of these for the last two weeks on my SMP box.
This panic is on -CURRENT from earlier today. Scheduler is ULE.
lock order reversal
1st 0xc047f820 sched lock (sched lock) @ /usr/src/sys/kern/kern_intr.c:548
2nd 0xc04b83c0 sio (sio) @ /usr/src/sys/dev/sio/sio.c:3242
Stack
