Date: Thu, 22 Feb 2001 13:08:37 +0200 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Dag-Erling Smorgrav <des@ofug.org> Cc: current@FreeBSD.org, jhb@FreeBSD.org, "Alexander N. Kabaev" <ak03@gte.com> Subject: A possible bug in the interrupt thread preemption code [Was: Kernel panic in irq14: ata0] Message-ID: <3A94F335.6C858C2@FreeBSD.org> References: <200102201821.TAA76890@freebsd.dk> <3A92B63B.B308C616@FreeBSD.org> <xzp66i5gp9y.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav wrote: > Maxim Sobolev <sobomax@FreeBSD.ORG> 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 syncing disks... -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A94F335.6C858C2>