----- Original Message -----
From: "Hiten Pandya" <[EMAIL PROTECTED]>
To: "Alexey Zelkin" <[EMAIL PROTECTED]>
Cc: "Poul-Henning Kamp" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, February 10, 2003 12:38 PM
Subject: Re: kld problem ? (was: Re: MSDOSFS wastes 256k when nothing is
mounted!)
> On Sun, Feb 09, 2003 at 10:16:21PM +0200, Alexey Zelkin wrote the words in
effect of:
> > hi,
> >
> > On Sun, Feb 09, 2003 at 08:39:59PM +0100, Poul-Henning Kamp wrote:
> >
> > > /*ARGSUSED*/
> > > int
> > > msdosfs_init(vfsp)
> > > struct vfsconf *vfsp;
> > > {
> > > dehashtbl = hashinit(desiredvnodes/2, M_MSDOSFSMNT, &dehash);
> > > mtx_init(&dehash_mtx, "msdosfs dehash", NULL, MTX_DEF);
> > > return (0);
> > > }
> >
> > BTW, it reminds me a problem I found last month. If you've MSDOSFS
> > compiled in kernel and try to load msdosfs.ko with loader -- then
> > you're 100% will hit into 'mutex already initialized' (or something
> > like that) panic later in boot process. (i.e. msdosfs_init() is called
> > twice for some reason)
> >
> > I not sure if it's applicable to KLDs at all or to msdosfs only.
>
> This also happens when the Linux kernel module is loaded twice.
> Cheers.
I've seen this occur with at least one device/pseudodevice module before: if
I both compiled itinto my kernel and have it loaded in /boot/loader.conf, my
machine panics almost immediately.
At the time I just assumed I was being a moron for trying to load the same
driver twice, two different ways, and disabled the kld. If this isn't
supposed to happen I'll go back and try to find the modules that gave me
problems.
(I *think* it was either random.ko or procfs.ko).
--Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
