Date: Tue, 13 May 2003 13:29:18 -0400 From: Michael Edenfield <kutulu@kutulu.org> To: Lars Eggert <larse@ISI.EDU> Cc: Dag-Erling Smorgrav <des@ofug.org> Subject: Re: 5.1-RELEASE TODO Message-ID: <20030513172918.GA13561@basement.kutulu.org> In-Reply-To: <3EC122B3.3000301@isi.edu> References: <200305131300.h4DD0Ecd059610@fledge.watson.org> <xzpof26vnds.fsf@flood.ping.uio.no> <3EC122B3.3000301@isi.edu>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] * Lars Eggert <larse@ISI.EDU> [030513 12:52]: > Dag-Erling Smorgrav wrote: > >I'm unable to reproduce this; kldload refuses to load a module which > >is already present, and if you try to preload a driver which is > >compiled into the kernel, the kernel will refuse to register it. > > I've seen panics like this happen with loading such duplicate modules > via /boot/loader.conf (i.e. not with kldload from the console.) Is this > what you mean by "preload"? > > It doesn't happen for all modules, but it does for some. I think I > remember random.ko being one that caused problems, but I'm not sure, and > can't test right now (away from the machine). Yes, it still happens. If 'device random' is in the kernel and 'random_load="YES"' in loader.conf then your machine panics on boot. I uncommented one too many lines in my kernel config yesterday and got bitten by this once again. --Mike [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+wStsCczNhKRsh48RAlr8AJ4zCPoYCL6X/aEEbchhFUUDCY59CQCgvMHQ npSZTc1PL8RFZkFtdb6+gWI= =dRMh -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030513172918.GA13561>