From owner-freebsd-bugs Fri May 23 21:08:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04751 for bugs-outgoing; Fri, 23 May 1997 21:08:33 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04737 for ; Fri, 23 May 1997 21:08:26 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.5/3.4W4) with ESMTP id NAA06741; Sat, 24 May 1997 13:07:08 +0900 (JST) Message-Id: <199705240407.NAA06741@gneiss.eps.nagoya-u.ac.jp> To: smurfen@ludd.luth.se Cc: freebsd-bugs@hub.freebsd.org, kato@eclogite.eps.nagoya-u.ac.jp Subject: Re: kern/3611: Internal CPU cache on CyrixiInstead DX2 does not work In-Reply-To: Your message of "Fri, 23 May 1997 15:21:12 +0200 (MET DST)" References: X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 24 May 1997 13:07:07 +0900 From: KATO Takenori Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Ola Persson Subject: Re: kern/3611: Internal CPU cache on CyrixiInstead DX2 does not work Date: Fri, 23 May 1997 15:21:12 +0200 (MET DST) > Ok, I send it to you only, if it should be sent to -bugs, just fwd it. I Cc to freebsd-bugs. > With Internal cache set to write-back (works) > > CCR1=90 > CCR2=0 > CCR3=0CR0=8005003b > > With internal cache set to write-thru (makes system crash) > > CCR1=90 > CCR2=16 > CCR3=0CR0=a005003b Firstly, I think former is write-through case, because latter one shows that (1) NW (not write-through) is set and (2) WB interface pin is enabled. If former is write-through, CCR1, CCR2and CR0 seem to be normal. > I tried to compile a program just to see if the error was still there and > it immediately put me in DDB. Maybe it is after such a panic you would > like me to run show cyrixreg ? Hmm I just thought about that now... I'll > Postpone this mail and do it right away.... > > First error while compiling didn't put me in ddb. > Operands given don't match any known 386 instruction > > continuing..... > > Second error while compiling the same program as above > (../../kern/tty_pty.c) > cc: Internal compiler error: Program cc1 got fatal signal 11 > and it dumped core. > > continuing.... > > Third error while compiling ../../kern/vfs_init.c > > Operands given don't match any known 386 instruction > > Damn computer refuses to panic just cuz I want it to. Anyway I guess this > proves that there is an error. When I get it to dump into ddb I'll write > down the result of a show cyrixreg. There are two reason for strange signal 11 on Cyrix CPU: (1) Motherboard and memory problem. (c.f. http://www.bitwizard.nl/sig11/) (2) CPU bug. Page fault address in CR2 register is sometimes (i.e. not always) collapsed by interruption and trap_pfault cannot get correct address (CR2 is zeroed by interruption). This can be fixed by converting of exception 14 handler from task gate to interrupt gate. Fix is only in PC-98 tree now. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) -------------------