Date: Tue, 13 Apr 1999 09:02:28 -0700 (PWT) From: Matthew Jacob <mjacob@feral.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: alpha@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Hmm... still NFS problems for Alpha? Message-ID: <Pine.LNX.4.04.9904130902050.27969-100000@feral-gw> In-Reply-To: <14099.23071.173949.334509@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > *after* the VM patch, I still get: > > > > make depend && make > > cc -c -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include > > opt_global.h -UKERNEL ../../alpha/alpha/genassym.c > > cc -static -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include > > opt_global.h genassym.o -o genassym > > ./genassym >assym.s > > Illegal instruction - core dumped > > *** Error code 132 > > > > Stop. > > farrago.feral.com > uname -a > > FreeBSD farrago.feral.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Apr 12 > > 23:02:43 PDT 1999 mjacob@farrago.feral.com:/tmp/sys/compile/FARRAGO > > alpha > > > > (same source builds in local or mfs based filesystems fine) > > > > > > Anybody else still having NFS problems with alpha? > > If the VM patch you mean is #if'ing out the pmap_zero_page_area() > calls in vm_page_set_validclean(), then no. I've just built one > kernel on a client with the patch, running -current as of 5am EDT. > The build directory was clean, and mounted (along with all of > /usr/src) from a 300Mhz PII server running FreeBSD-current as of March > 25th or so. > Hmm. I wonder what's going on then? Well, I'll look at it again tonite... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.04.9904130902050.27969-100000>