Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-26 Thread Maxim Sobolev
John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > >> > >> A recursive sched_lock? Erm, well, stick these options in your kernel > >> config: > >> > >> options KTR > >> options KTR_EXTEND > >> options KTR_COMPILE=KTR_LOCK > >> options

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Maxim Sobolev
John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > >> >> > Here it is (from DDB): > >> >> > panic(c027de93,c0297409,c027f878,368,80286) > >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> >> > mi_switch(c32c5da0,

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread John Baldwin
On 22-Feb-01 Maxim Sobolev wrote: > John Baldwin wrote: >> >> A recursive sched_lock? Erm, well, stick these options in your kernel >> config: >> >> options KTR >> options KTR_EXTEND >> options KTR_COMPILE=KTR_LOCK >> options KTR_MASK=KTR_MASK > > Bah, it even do

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Maxim Sobolev
John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > >> >> > Here it is (from DDB): > >> >> > panic(c027de93,c0297409,c027f878,368,80286) > >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> >> > mi_switch(c32c5da0,

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Maxim Sobolev
John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > >> >> > Here it is (from DDB): > >> >> > panic(c027de93,c0297409,c027f878,368,80286) > >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> >> > mi_switch(c32c5da0,

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread John Baldwin
On 22-Feb-01 Maxim Sobolev wrote: > John Baldwin wrote: > >> On 22-Feb-01 Maxim Sobolev wrote: >> >> >> > Here it is (from DDB): >> >> > panic(c027de93,c0297409,c027f878,368,80286) >> >> > _mtx_assert(c02ea000,9,c027f878,368,80286) >> >> > mi_switch(c32c5da0,3,c02cea44,c357be98) >> >> > ithread_

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Maxim Sobolev
John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > >> > Here it is (from DDB): > >> > panic(c027de93,c0297409,c027f878,368,80286) > >> > _mtx_assert(c02ea000,9,c027f878,368,80286) > >> > mi_switch(c32c5da0,3,c02cea44,c357be98) > >> > ithread_schedule(c0747c00,1) > >> > sched_ithd(e) > >>

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread John Baldwin
On 22-Feb-01 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> On 22-Feb-01 Maxim Sobolev wrote: >> > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. >> Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. > > For the same reason,

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Dag-Erling Smorgrav
John Baldwin <[EMAIL PROTECTED]> writes: > On 22-Feb-01 Maxim Sobolev wrote: > > It's already have INVARIANTS, MUTEX_DEBUG, WITNESS and WITNESS_DDB. > Hmm, ouch, you do'nt want MUTEX_DEBUG, that'll slow your system to a crawl. For the same reason, you probably want WITNESS_SKIPSPIN. WITNESS_DDB

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread John Baldwin
On 22-Feb-01 Maxim Sobolev wrote: >> > Here it is (from DDB): >> > panic(c027de93,c0297409,c027f878,368,80286) >> > _mtx_assert(c02ea000,9,c027f878,368,80286) >> > mi_switch(c32c5da0,3,c02cea44,c357be98) >> > ithread_schedule(c0747c00,1) >> > sched_ithd(e) >> > Xresume14() >> > --- interrupt, ei

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Maxim Sobolev
John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > John Baldwin wrote: > > > >> On 22-Feb-01 Maxim Sobolev wrote: > >> > Dag-Erling Smorgrav wrote: > >> > > >> >> Maxim Sobolev <[EMAIL PROTECTED]> writes: > >> >> > It's not an ata specific problem, but rather a problem of all ISA > >> >>

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread John Baldwin
On 22-Feb-01 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> On 22-Feb-01 Maxim Sobolev wrote: >> > Dag-Erling Smorgrav wrote: >> > >> >> Maxim Sobolev <[EMAIL PROTECTED]> writes: >> >> > It's not an ata specific problem, but rather a problem of all ISA >> >> > devices (

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread John Baldwin
On 22-Feb-01 Maxim Sobolev wrote: > John Baldwin wrote: > >> On 22-Feb-01 Maxim Sobolev wrote: >> > Dag-Erling Smorgrav wrote: >> > >> >> Maxim Sobolev <[EMAIL PROTECTED]> writes: >> >> > It's not an ata specific problem, but rather a problem of all ISA >> >> > devices (I have an ISA based ata c

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Maxim Sobolev
John Baldwin wrote: > On 22-Feb-01 Maxim Sobolev wrote: > > Dag-Erling Smorgrav wrote: > > > >> Maxim Sobolev <[EMAIL PROTECTED]> writes: > >> > It's not an ata specific problem, but rather a problem of all ISA > >> > devices (I have an ISA based ata controller). > >> > >> I don't think it has an

Re: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread Dag-Erling Smorgrav
John Baldwin <[EMAIL PROTECTED]> writes: > On 22-Feb-01 Maxim Sobolev wrote: > > Dag-Erling Smorgrav wrote: > > > >> Maxim Sobolev <[EMAIL PROTECTED]> writes: > >> > It's not an ata specific problem, but rather a problem of all ISA > >> > devices (I have an ISA based ata controller). > >> > >> I

RE: A possible bug in the interrupt thread preemption code [Was:

2001-02-22 Thread John Baldwin
On 22-Feb-01 Maxim Sobolev wrote: > Dag-Erling Smorgrav wrote: > >> Maxim Sobolev <[EMAIL PROTECTED]> writes: >> > It's not an ata specific problem, but rather a problem of all ISA >> > devices (I have an ISA based ata controller). >> >> I don't think it has anything to do with ISA. I've had sim

A possible bug in the interrupt thread preemption code [Was: Kernel panic in irq14: ata0]

2001-02-22 Thread Maxim Sobolev
Dag-Erling Smorgrav wrote: > Maxim Sobolev <[EMAIL PROTECTED]> writes: > > It's not an ata specific problem, but rather a problem of all ISA > > devices (I have an ISA based ata controller). > > I don't think it has anything to do with ISA. I've had similar > problems on a PCI-only system (actual