From owner-freebsd-hackers Wed Mar 26 21:18:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA05163 for hackers-outgoing; Wed, 26 Mar 1997 21:18:36 -0800 (PST) Received: from remington.mt.cs.keio.ac.jp (remington.mt.cs.keio.ac.jp [131.113.82.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA05156 for ; Wed, 26 Mar 1997 21:18:31 -0800 (PST) Received: (from hosokawa@localhost) by remington.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id OAA24086; Thu, 27 Mar 1997 14:18:13 +0900 Date: Thu, 27 Mar 1997 14:18:13 +0900 Message-Id: <199703270518.OAA24086@remington.mt.cs.keio.ac.jp> To: bde@zeta.org.au Cc: freebsd-hackers@freebsd.org, hosokawa@mt.cs.keio.ac.jp Subject: Re: 2.2.1 Serious boot problem related to i586_copy* In-Reply-To: Your message of "Thu, 27 Mar 1997 15:31:46 +1100". <199703270431.PAA09205@godzilla.zeta.org.au> From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) 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... I'm not familiar with NPX instruction, but I think i586_bcopy or something depends on the NPX's initialization by BIOS. -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan