Date: Tue, 22 Oct 2002 12:15:09 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: kalts@estpak.ee Cc: Maxime Henrion <mux@freebsd.org>, Vitaly Markitantov <vm@dics.com.ua>, jhb@freebsd.org, current@freebsd.org Subject: Re: smbfs broken? Message-ID: <3DB5A3BD.77138903@mindspring.com> References: <20021022110135.GA31643@iron.del.local> <20021022112320.GF26605@elvis.mu.org> <20021022142954.GA3206@tiiu.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
Vallo Kallaste wrote:
> On Tue, Oct 22, 2002 at 04:23:20AM -0700, Maxime Henrion
> <mux@freebsd.org> wrote:
>
> [snip]
> > It would help a lot if you could provide a traceback.
>
> This is the one I'm seeing everytime while trying to copy file from
> ro smbfs mount. -current is about four days old, smbfs.ko _is_
> compiled with -DSMP and in sync with kernel.
[ ... ]
Everyone is reporting a bug similar to this; it is probably a problem
in the memory allocator.
> #11 0xc039b272 in trap_pfault (frame=0xdf9b6724, usermode=0, eva=2)
> at ../../../i386/i386/trap.c:760
> #12 0xc039ace2 in trap (frame=
> {tf_fs = -1053753320, tf_es = 16, tf_ds = -543490032, tf_edi = -1001077964, tf_esi = -543463582, tf_ebp = -543463580, tf_isp = -543463600, tf_ebx = 0, tf_edx = -543461984, tf_ecx = 0, tf_eax = 14, tf_trapno = 12, tf_err = 0, tf_eip = 2, tf_cs = 8, tf_eflags = 66178, tf_esp = -543463520, tf_ss = -1001019794})
> at ../../../i386/i386/trap.c:446
> #13 0xc0383f58 in calltrap () at {standard input}:99
> #14 0xc455a66e in ?? ()
> #15 0xc455a072 in ?? ()
> #16 0xc4559e87 in ?? ()
> #17 0xc45609f8 in ?? ()
If you are running the smbfs.ko, either load the module symbols into
gdb before asking for the traceback, or statically compile SMBFS into
the kernel. We need the intermediate code.
> #18 0xc035947d in vnode_pager_getpages (object=0x0, m=0x0, count=0, reqpage=0)
...though the fact that this happened agains the vn device on
an SMBFS from a file write is pretty indicative that you are running
a vnconfig'ed device on top of an SMBFS file. This is probably not a
good thing to do.
It would be nice if you could give us more information as to exactly
what it is you are doing, logically, to cause this problem; as things
sit, it seems you are doing some evil things.
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB5A3BD.77138903>