Date: Mon, 16 Aug 2004 17:03:18 -0700 From: "George V. Neville-Neil" <gnn@neville-neil.com> To: "Rob MacGregor" <freebsd.macgregor@blueyonder.co.uk> Cc: current@freebsd.org Subject: Re: lnc0 in VmWare doesn't work Message-ID: <m2657iljg9.wl@minion.local.neville-neil.com> In-Reply-To: <200408162111.i7GLBRbj017293@the-macgregors.org> References: <4120EC70.9050804@FreeBSD.org> <200408162111.i7GLBRbj017293@the-macgregors.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Mon, 16 Aug 2004 22:11:38 +0100, Rob MacGregor wrote: > > Sergey Matveychuk [sem@freebsd.org] danced on the keyboard and produced: > > > Vitaly Markitantov wrote: > > > >> I found what is the cause of problem with lnc0. > >> it's commited vm_contig.c from Thu Aug 5 14:54:12 PDT 2004 ( > >> http://lists.freebsd.org/pipermail/cvs-src/2004-August/028854.html ) > >> > >> I set in /boot/loader.conf > >> vm.old_contigmalloc="1" > >> and all stuff works fine. > > > > It does not work for me. I guess if you'll rebuild your > > kernel with new > > drivers it could stops work for you too. > > Happy to say that it did however work for me - source from this morning (circa > 09:00 GMT) and VMWare 4.5.2. Not to say "me too" but "me too." So, do we need to fix the lance driver to handle this? Will this bite us easily on other drivers? Later, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2657iljg9.wl>