Date: Wed, 31 Jul 2002 09:24:39 -0500 From: Steve Peterson <stevep-hv@virtation.com> To: Andy Sparrow <spadger@best.com>, stable@freebsd.org Subject: Re: Problems with mount_smbfs Message-ID: <5.1.0.14.2.20020731092326.0375a348@209.46.51.22> In-Reply-To: <20020731022326.0F45524@CRWdog.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
FWIW, I'm getting the same problem when trying to mount, using RELENG_4_6 from about July 10. Haven't had the time to troubleshoot it to any degree, though. S \At 10:23 PM 7/30/2002 -0400, Andy Sparrow wrote: >Hi, > >I've been getting the following for the last few weeks in -STABLE when trying >to mount a SMB share; the first attempt gives: > >bash-2.05a# mount_smbfs -I server -W <domain> //user@server/share /mnt >mount_smbfs: vfsload(smbfs): Exec format error > >kldstat shows: > >bash-2.05a# kldstat >Id Refs Address Size Name > 1 15 0xc0100000 307e54 kernel > 2 1 0xc0408000 8cb0 snd_maestro3.ko > 3 1 0xc0411000 1880c snd_pcm.ko > 4 1 0xc1d34000 7000 linprocfs.ko > 5 1 0xc1dc4000 2000 blank_saver.ko > 6 3 0xc1dc6000 14000 linux.ko > 7 1 0xc1e4a000 7d000 ltmdm.ko > 8 1 0xc1ed6000 2000 rtc.ko > 9 1 0xc1ee1000 9000 vmmon_up.ko >10 1 0xc1eec000 4000 if_tap.ko >11 4 0xc1ef3000 9000 netgraph.ko >12 1 0xc1f00000 3000 ng_ether.ko >13 1 0xc1f05000 4000 ng_bridge.ko >14 1 0xc1f0c000 3000 ng_socket.ko >16 1 0xc2a37000 3000 libiconv.ko > >and I get this on the console: > >module_register: module iconv already exists! >linker_file_sysinit "libiconv.ko" failed to register! 17 > > >Trying again, the message is different, I get > >module_register: module dev_netsmb already exists! >linker_file_sysinit "smbfs.ko" failed to register! 17 > >on the console, and kldstat shows: > >bash-2.05a# kldstat >Id Refs Address Size Name > 1 17 0xc0100000 307e54 kernel > 2 1 0xc0408000 8cb0 snd_maestro3.ko > 3 1 0xc0411000 1880c snd_pcm.ko > 4 1 0xc1d34000 7000 linprocfs.ko > 5 1 0xc1dc4000 2000 blank_saver.ko > 6 3 0xc1dc6000 14000 linux.ko > 7 1 0xc1e4a000 7d000 ltmdm.ko > 8 1 0xc1ed6000 2000 rtc.ko > 9 1 0xc1ee1000 9000 vmmon_up.ko >10 1 0xc1eec000 4000 if_tap.ko >11 4 0xc1ef3000 9000 netgraph.ko >12 1 0xc1f00000 3000 ng_ether.ko >13 1 0xc1f05000 4000 ng_bridge.ko >14 1 0xc1f0c000 3000 ng_socket.ko >16 2 0xc2a37000 3000 libiconv.ko >17 1 0xc2a1d000 1a000 smbfs.ko >18 1 0xc2a3a000 3000 libmchain.ko > > >Errr. This used to work, as recently as about ~4-5 weeks ago, but has been >failing for a few weeks now. Kernel config included: > >options NETSMB #SMB/CIFS requester >options NETSMBCRYPTO #encrypted password support for SMB > >options LIBMCHAIN #mbuf management library >options LIBICONV > >so I'm really stumped as to why the kernel is even trying to load the modules >(which are up-to-date with the kernel & userland, on a cvsup from last night, >29th July, BTW). libiconv was portupgraded, and made no difference to the >symptoms. > > >I read the archives, and this seemed to be a problem circa 4.5-RELEASE, >someone at that time suggested that not statically compiling NETSMB into the >kernel helped. I left only NETSMBCRYPTO in the kernel (as the other 3 have >KLMs), and got this entirely repeatable crash-on-boot (pardon typing): > > >Booting [kernel]... >Copyright (c) 1992-2002 The FreeBSD Project >Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x0 >fault code = supervisor read, page not present >instruction pointer = 0x8:0xc0183f09 >stack pointer = 0x10:0xc0440fb4 >frame pointer = 0x10:0xc0440fc0 >code segment = bane 0x0, limit 0xfffff, type 0x16 > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >Current process = Idle >kernel: type 12 trap, code = 0 >Stopped at 0xc0183f09: movl 0(%esi),%ebx > >db> trace > >(null)(0) at 0xc0183f09 >(null)(c035ec84,c0440ff8,c0128ed0) at 0xc0188444d >(null)(0,0,0,0,0) at 0xc016f200 >(null)() at 0xc0128ed0 > > >Loading the modules into the kernel from the loader gives precisely the same >results, e.g. no boot with that kernel. > >Anyone got any suggestions? > >Regards, > >AS > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.2.20020731092326.0375a348>