smbfs.ko regression?
Thomas Backman
serenity at exscape.org
Thu Jun 18 16:48:29 UTC 2009
Has anyone else had trouble with smbfs.ko/samba mounting recently?
I upgraded to r194428 today, and on reboot noticed that the computer
had hanged (i.e. took way too long to boot), so I plugged a monitor in
and noticed that it had hanged on loading the smbfs module/mounting a
smbfs share, and then the same thing happened on "mounting late
filesystems" (dmesg -a | grep late returns nothing now that it works,
BTW). IIRC it dropped to single-user due to "/etc/rc returing an
error" or something to that matter. I commented the line out in fstab
and did an "exit" and it came up from single user beautifully.
The error appears to be a bit random and I haven't been able to
reproduce it, but it happened two or three times so it wasn't just a
one-off. It did print some kind of error, but I guess there's no way
of getting at that now?
On a similar note, I can't kldunload it, either. The computer just
freezes - it responds to ping, but not SSH input, and not keyboard
input either (not even drop to debugger). I can't find a way out
except to reset it. I don't really care too much about this part, but
freezes are bad. Needless to say I can't provide a backtrace or
similar - is there anything I can do to help? Still, the main issue,
and question, is regarding the *loading*.
[root at chaos ~]# mount|grep smbfs
//SERENITY at EXSCAPE/FBSDBACKUP on /mnt/backup (smbfs)
[root at chaos ~]# umount /mnt/backup
[root at chaos ~]# mount|grep smbfs
[root at chaos ~]# kldstat
Id Refs Address Size Name
1 21 0xffffffff80100000 e61c98 kernel
2 1 0xffffffff80f62000 50ae98 zfs.ko
3 2 0xffffffff8146d000 7988 opensolaris.ko
4 1 0xffffffff81475000 3378 accf_http.ko
5 1 0xffffffff81479000 4278 amdtemp.ko
6 1 0xffffffff81622000 722e1 smbfs.ko
7 2 0xffffffff81695000 6694 libiconv.ko
8 2 0xffffffff8169c000 1740 libmchain.ko
[root at chaos ~]# kldunload smbfs
After quite a while: Read from remote host 192.168.1.10: Connection
reset by peer
"kldunload amdtemp" succeeds, by the way.
Regards,
Thomas
More information about the freebsd-current
mailing list