Re: smbfs problems?

[YONETANI Tomokazu <qhwt+dragonfly-bugs@xxxxxxxxxx>]

Hi.

On Thu, Mar 18, 2004 at 11:59:37AM +0000, Adam K Kirchhoff wrote:
> >> 	Add LIBMCHAIN  and LIBICONV options to your kernel config
> >> 	too.  All mb_* errors are resulting from that, and so are
> >> 	the iconv_* errors.
> 
> > New problem :-)
> 
> > If I boot up and have loader.conf load libiconv, libmchain, and smbfs,
> > the kernel panic:
> 
> > http://memory.visualtech.com/errors.txt
> 
> > If I don't load them, and then try to mount a samba share, I get:
> 
> > [ root@sorrow - /home/adamk ]: mount_smbfs //adamk@thorn/Media /mnt
> > mount_smbfs: vfsload(smbfs): File exists
> 
> Alright, so is anyone actually successfully using smbfs at the moment?
>
> If so, what kernel options are you using, and what modules do you have
> installed?  Can you show a directory listing for /dev/nsmb*?

Can you try either of the following, if you're not?
A) compile these three drivers in the kernel and don't rely on the
   modules, or
B) completely remove these options from your kernel config file
   and try loading modules one by one using kldload.

I'm doing B) and it seems to be working.

I think our module dependency tracking system is not working very well
yet. If I put
  libiconv_load="YES"
  libmchain_load="YES"
  smbfs_load="YES"
in /boot/loader.conf, the boot loader fails to load smbfs saying
libmchain has unexpected module version. This seems to me to be because
our MODULE_VERSION() is defined as no-op in /sys/sys/module.h, but I'm
not sure.