From owner-freebsd-hackers  Wed Mar 26 21:56:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA07178
          for hackers-outgoing; Wed, 26 Mar 1997 21:56:59 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA07173
          for <freebsd-hackers@freebsd.org>; Wed, 26 Mar 1997 21:56:51 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA23929; Wed, 26 Mar 1997 21:56:40 -0800 (PST)
To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
cc: bde@zeta.org.au, freebsd-hackers@freebsd.org
Subject: Re: 2.2.1 Serious boot problem related to i586_copy* 
In-reply-to: Your message of "Thu, 27 Mar 1997 14:18:13 +0900."
             <199703270518.OAA24086@remington.mt.cs.keio.ac.jp> 
Date: Wed, 26 Mar 1997 21:56:39 -0800
Message-ID: <23922.859442199@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> In article <199703270431.PAA09205@godzilla.zeta.org.au>
> bde@zeta.org.au writes:
> 
> >> "flags npx0 0x07" also disables i586_bcopy and i586_bzero.  Are those
> >> broken too?
> 
> Sorry, 0x07 is overkilling solution.  I tested all combinations now.
> 
> 	0x00	Hangup
> 	0x01	OK
> 	0x02	Hangup
> 	0x03	OK
> 	0x04	Hangup
> 	0x05	OK
> 	0x06	Hangup
> 	0x07	OK
> 
> This result implys i586_bcopy is the source of this problem.  
> Hmm...

Well, I've already amended the documentation at your request
once - do you want me to amend it again? :-)

						Jordan