From owner-freebsd-hackers  Wed Mar 26 20:51:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA04033
          for hackers-outgoing; Wed, 26 Mar 1997 20:51:55 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04028
          for <freebsd-hackers@freebsd.org>; Wed, 26 Mar 1997 20:51:52 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA09205; Thu, 27 Mar 1997 15:31:46 +1100
Date: Thu, 27 Mar 1997 15:31:46 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703270431.PAA09205@godzilla.zeta.org.au>
To: freebsd-hackers@freebsd.org, hosokawa@mt.cs.keio.ac.jp
Subject: Re: 2.2.1 Serious boot problem related to i586_copy*
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I found the reason of a serious boot problem I reported yesterday.  On
>some Pentium machines (as far as I know Panasonic AL-N1, and Rios
>Chandler), i586_copyout and i586_copyin does not work and they causes
>system hangup before starting sysinstall.
>
>This problem can be avoided by specifying "flags npx0 0x07" from
>UserConfig CLI mode.

"flags npx0 0x07" also disables i586_bcopy and i586_bzero.  Are those
broken too?

I don't see how i586_copyout or i586_copyin could be broken on any
real Pentium machine.  i586_bcopy and i586_bzero might not work for
device memory, but extensive (:-) testing in 2.2ALPHA/BETA/GAMMA
didn't show any problems.

Bruce