From owner-freebsd-current Thu Feb 24 18:57:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 64FBA37BC1A; Thu, 24 Feb 2000 18:57:21 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from 1Cust232.tnt4.waldorf.md.da.uu.net (localhost [127.0.0.1]) by builder.freebsd.org (Postfix) with ESMTP id 9EAD2132DD; Thu, 24 Feb 2000 18:55:28 -0800 (PST) Date: Thu, 24 Feb 2000 21:57:16 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Mike Smith Cc: Soren Schmidt , Yarema , FreeBSD Current Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002250242.SAA00981@mass.cdrom.com> 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, Mike Smith wrote: > > > I'd hazard a guess that the presence of modules is causing the kernel > > > linker to run and pull all the sysctl hooks for modules it's finding. > > > I'm probably wrong, just a guess. > ... > > I'll go look up cold usage, and see if it necessarily has to be done that > > early. I'll also investigate that sysctl possibility. > > Oops. I meant sysinit, not sysctl. Well, I don't think that's it. I've tried moving it around a bit. None of the code is called until the intrhook handler is called back, so I don't see how it can be the sysinit itself causing the failure. > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message