Date: Tue, 10 Jun 2003 01:20:48 -0700 From: Hiten Pandya <hmp@FreeBSD.ORG> To: Martin Blapp <mb@imp.ch> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/boot/i386/libi386 i386_module.c Message-ID: <20030610082048.GA60290@perrin.int.nxad.com> In-Reply-To: <20030509202516.J23311@cvs.imp.ch> References: <XFMail.20030509134912.jhb@FreeBSD.org> <20030509202516.J23311@cvs.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 09, 2003 at 08:27:32PM +0200, Martin Blapp wrote: > > Hi, > > > Trying to kldload something that is already present in the kernel > > either fails or results in a kernel panic. If you are already > > rebooting to test it, then you might as well build a new kernel > > as a new module each time. > > I thought there were patches posted to CURRENT to address this > issue ? Nobody seems to have them comitted, unfortunatly. It seems, that loading something at boot time would create such an issue; but at run time, if you try to kldload something which is already present in the kernel, than it errors out. I recently posted a workaround to re@ for fixing the case where multiple modules of the same type with different filenames could be loaded and the machine could go boom; but it seems that the kern_linker.c code is a little messed up in its current state, so there are more cleanups required to be done before such workaround/fix can be committed. Cheers. -- Hiten (hmp@FreeBSD.ORG)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030610082048.GA60290>