Date: Fri, 2 Apr 2004 17:35:41 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Hilko Meyer <Hilko.Meyer@gmx.de> Cc: current@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode with samba Message-ID: <20040402173415.D43338@carver.gumbysoft.com> In-Reply-To: <a6em605jobp869oskujuf0vetfdi2qm5bn@smtp.compuserve.de> References: <hme360h63t43dr1j51nhcl6s89n51mrh47@4ax.com> <3ll6601p9n67rm3hk9mvutc8qjidatjp9j@smtp.compuserve.de> <f55960147gk3qka92er1iflc0s20vvrlm3@smtp.compuserve.de> <jp3h60hfn9bjbt93lah355t7i04p524b6q@smtp.compuserve.de> <a6em605jobp869oskujuf0vetfdi2qm5bn@smtp.compuserve.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 31 Mar 2004, Hilko Meyer wrote: > Doug White schrieb: > >I haven't had time to look at this. > > > >Can y ou try it with -CURRENT, if you ahve't already? > > I can, but I don't want to do that. And it's no longer necessary. I've > installed the recent update of the samba 2.2.8 port this evening and > discovered the reason of the panic at the time. I was able to reproduce this with -current, but looking at the code I don't understand how that vfs op is getting nulled out. It should be set to the default operation which just return EOPNOTSUPP. I guess some KASSERTs are in order. The function itself hasn't changed materially in months, so its hard to tell when this crept in. Out of curiousity, do you have a -stable box around, and can you reproduce on that? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040402173415.D43338>