From owner-freebsd-hackers  Wed Mar 26 21:53:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA07018
          for hackers-outgoing; Wed, 26 Mar 1997 21:53:21 -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 VAA07012
          for <freebsd-hackers@freebsd.org>; Wed, 26 Mar 1997 21:53:17 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA11880; Thu, 27 Mar 1997 16:45:49 +1100
Date: Thu, 27 Mar 1997 16:45:49 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703270545.QAA11880@godzilla.zeta.org.au>
To: bde@zeta.org.au, hosokawa@mt.cs.keio.ac.jp
Subject: Re: 2.2.1 Serious boot problem related to i586_copy*
Cc: freebsd-hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Sorry, 0x07 is overkilling solution.  I tested all combinations now.
>
>	0x00	Hangup
>	0x01	OK
>...
>This result implys i586_bcopy is the source of this problem.  
>Hmm...
>
>I'm not familiar with NPX instruction, but I think i586_bcopy or
>something depends on the NPX's initialization by BIOS.

FreeBSD initializes it before using it.

Try defining bcopyw and bcopy as bcopyb in syscons, and using pcvt.
bcopyw is currently defined as bcopy.  Undef'ing it won't work, since
bcopyw() went away.  There are some bcopy's that should probably be
bcopyw's or bcopyb's.  pcvt uses bcopyb in just one place for accessing
character sets.

Bruce