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 anything to do with ISA. I've had similar
> >> problems on a PCI-only system (actually, PCI+EISA motherboard with no
> >> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all
> >> SCSI).
> >>
> >> Considering that backing out rev 1.14 of ithread.c eliminates the
> >> panics, and that that revision is supposed to enable interrupt thread
> >> preemption, and that the crashed kernels show signs of stack smashing,
> >> I'd say the cause is probably a bug in the preemption code.
> >
> > Update: the bug is still here, as of -current from 22 Feb. Hovewer, this time
> > it even doesn't let to boot into single-user with following panic message:
> > kernel trap 12 with interrupts disabled
> > panic: mutex sched lock recursed at ../../kern/kern_synch.c:872
> Errrr.  That would be something that is leaking sched_lock.  Hmm...
> Got a backtrace?  What is really annoying is that preemption has been in the
> kernel since Feb 1.  I just accidentally turned it off in the ithread code
> reorganization and then turned it back on.  It was off for a few hours after
> only being on for 2 weeks, and now everyone magically has problems.

Here it is (from DDB):
--- interrupt, eip = 0xc025b60f, esp = 0x80296, ebp = 0xc357bf08 ---
trap(18, 10, 10,c01597b6,20)
--- trap 0x9, eip = 0xc025a5de, esp = 0xc357bf50, ebp = 0xc357bf64 ---


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to