From owner-freebsd-current Tue Feb 20 10:53: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id DCC0E37B401; Tue, 20 Feb 2001 10:52:58 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id TAA35414; Tue, 20 Feb 2001 19:52:58 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Maxim Sobolev Cc: Soren Schmidt , current@FreeBSD.ORG, sos@FreeBSD.ORG, jhb@FreeBSD.ORG, "Alexander N. Kabaev" Subject: Re: Kernel panic in irq14: ata0 References: <200102201821.TAA76890@freebsd.dk> <3A92B63B.B308C616@FreeBSD.org> From: Dag-Erling Smorgrav Date: 20 Feb 2001 19:52:57 +0100 In-Reply-To: Maxim Sobolev's message of "Tue, 20 Feb 2001 20:23:55 +0200" Message-ID: Lines: 17 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev 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. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message