From owner-freebsd-current Thu Feb 24 1: 1:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 5FEFA37BAED; Thu, 24 Feb 2000 01:01:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12Nu8o-000Mhw-0X; Thu, 24 Feb 2000 09:00:59 +0000 Received: from tecra.nlsystems.com (tecra [10.0.0.5]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA94982; Thu, 24 Feb 2000 09:04:02 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 24 Feb 2000 09:03:55 +0000 (GMT) From: Doug Rabson To: Soren Schmidt Cc: Mike Smith , Yarema , FreeBSD Current , sos@freebsd.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002240845.JAA86244@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Feb 2000, Soren Schmidt wrote: > It seems Mike Smith wrote: > > > Forgive me if I'm beating a dead horse... I'm still having the following > > > problem if I load any modules from /boot/loader.conf: > > > > I've reproduced this here, and narrowed it down to Soren's ATA megacommit > > on the 18th. Unfortunately, the newbus patches (tested) and the other > > gunk (untested) ended up lumped in together, and I'm not having a lot of > > luck working out what exactly might be causing this. > > That megapatch was only newbus patches and cosmetics around that, one > new item was cmd646 support but that is hardly the problem here. > > > Soren - this is somewhat of a showstopper. Can you reproduce it there? > > Nope, I've tried several machines here, no problems, even with tons > of modules.. > > The only thing I can come up with is that _something_ makes the > delayed probe be called _before_ interrupts are up and running. > That will make it fail like this. Quuestion is is something > else messing with those hooks ? > We've seen this before, but back then no solution was found either, > it dissaperead all by itself... Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW. Nick spent a couple of hours looking at it without much success. I'll try some things today to see if the probe is being called with interrupts disabled. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message