From owner-freebsd-current Sat Apr 13 21:18:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA21418 for current-outgoing; Sat, 13 Apr 1996 21:18:11 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA21411 for ; Sat, 13 Apr 1996 21:18:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id VAA03036; Sat, 13 Apr 1996 21:18:01 -0700 (PDT) Message-Id: <199604140418.VAA03036@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: Can someone explain why... In-reply-to: Your message of "Sat, 13 Apr 1996 18:39:37 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 13 Apr 1996 21:18:00 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >...I get these occasionally while attempting to compile a kernel: > >freebsd# make >cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -g -nostdinc -I. -I../.. -I../../sys -I../../../include -DI486_CPU -DCOMPAT_43 -DDEVFS -DNFS -DFFS -DINET -DDODUMP -DKERN >EL ../../kern/subr_xxx.c >cc: Internal compiler error: program cc1 got fatal signal 10 >*** Error code 1 Seemingly random signal 10 and 11s almost always indicates a hardware problem. It's usually a problem with memory or the secondary cache, but has also been known to be caused by flakey disk controllers, motherboards, and CPUs. I don't think this is disk controller related because you are also having weird kernel panics in areas where I know no bugs exist. Several years ago we had some VM system problems which would sometimes cause similar behavior, but the causes of these problems are well understood and have been fixed for years. The only way to troubleshoot this kind of problem is to first look at your motherboard settings for correctness and then start replacing components until the problem goes away. I would try changing the memory first. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project