From owner-freebsd-current Thu Feb 22 4:21:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 87F0037B401; Thu, 22 Feb 2001 04:21:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1MCJ2l86660; Thu, 22 Feb 2001 04:19:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A94F335.6C858C2@FreeBSD.org> Date: Thu, 22 Feb 2001 04:20:56 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: RE: A possible bug in the interrupt thread preemption code [Was: Cc: "Alexander N. Kabaev" , current@FreeBSD.org, Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-01 Maxim Sobolev wrote: > Dag-Erling Smorgrav wrote: > >> 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. > > 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. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message