From owner-freebsd-current  Sun Jan 19 22:36:31 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA14500
          for current-outgoing; Sun, 19 Jan 1997 22:36:31 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA14494;
          Sun, 19 Jan 1997 22:36:19 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id RAA14932; Mon, 20 Jan 1997 17:31:28 +1100
Date: Mon, 20 Jan 1997 17:31:28 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701200631.RAA14932@godzilla.zeta.org.au>
To: peter@spinner.dialix.com, wpaul@freefall.freebsd.org
Subject: Re: VM bogon? Was: Re: NIS breakage
Cc: current@FreeBSD.org, dyson@FreeBSD.org, mark@grondar.za, peter@FreeBSD.org
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>BTW, are these failure cases happening on P5 or P6's?  Perhaps the
>fpu-based "fast" P5 copyin/copyout are to blame here?  Mark, if you are
>seeing this on a P5 machine and can reproduce this easily, try looking up

Didn't Mark say that this is on a 386? :-).  Don't blame the fpu-based
copyin/out if your are not sure.  It had enough real bugs in untagged
releases for a year of FUD.

>the option for NPX_DISABLE_I586_OPTIMIZED_COPYIO in npx.c and see if you
>can figure out how to configure npx's flags to disable this floating point.
> I think it's "device npx0 ..... flags 4"  or something like that.  Perhaps
>"flags 7" might be best to eliminate the possibility. 

See LINT.  I think it's "flags npx0 4" in userconfig.  npx0 is invisibile
in visual userconfig :-(.

Bruce