From owner-freebsd-stable Tue Dec 19 10:23:26 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA26673 for stable-outgoing; Tue, 19 Dec 1995 10:23:26 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA26668 for ; Tue, 19 Dec 1995 10:23:25 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA07627 for ; Tue, 19 Dec 1995 10:23:20 -0800 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA12428; Tue, 19 Dec 1995 10:21:22 -0800 From: "Rodney W. Grimes" Message-Id: <199512191821.KAA12428@GndRsh.aac.dev.com> Subject: Re: program cc1 got fatal signal 11 To: asami@cs.berkeley.edu (Satoshi Asami) Date: Tue, 19 Dec 1995 10:21:22 -0800 (PST) Cc: stable@freebsd.org In-Reply-To: <199512191220.EAA02774@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Dec 19, 95 04:20:29 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk > > I've seen cc1 occasionally die with signals (usually 11, but I've seen > 6 and 10 before too) on a 2.1R machine recently. Although I suspected > hardware problems, as it disappeared when I disabled the internal > cache (disabling the external cache only didn't help) on an ASUS > 55something (with PB cache) motherboard, I just saw it happen again on > a replacement board (forgot the manufacturer, made in USA, also uses > Triton), I thought I'd send you guys a note. > > The problem always occurs on the same file when I compile the kernel. > However, if I type "make", it will compile that file and goes on to > others as well, but it usually fails again after a few more files. > Also, according to the vendor's engineers, the ASUS board works fine > with 256K cache but not with 512K of cache. The replacement board > goes much further in compilation but still fails occasionally. > > Nothing except the motherboard and cache has changed. We tried two > CPUs (Pentium 133) on the first board with the same result. (That's > why it's so puzzling, as the problem disappeared when we disabled the > INTERNAL cache.) > > Anyone else seen something like this? Is it possible that an OS can > cause a problem like this, could it be something with cache > invalidation (just a wild guess)? (Thank god at least the vendor is > not pulling a "it works for DOS and Windows, so it is fine".) I strongly suspect hardware problems given that I have run 100's if not thousands of passes of make world on 2.1-stable since 2.1-release occured using ASUS PCI/I-P-55TP4XE's, including 512K cache 133Mhz setups. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD