From owner-freebsd-stable Sun Oct 1 19:19: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 91BA237B66C for ; Sun, 1 Oct 2000 19:19:00 -0700 (PDT) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id TAA73863; Sun, 1 Oct 2000 19:18:41 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200010020218.TAA73863@gndrsh.dnsmgr.net> Subject: Re: Signal 4 while compiling 4.1.1 In-Reply-To: <20001001190302.J27736@fw.wintelcom.net> from Alfred Perlstein at "Oct 1, 2000 07:03:02 pm" To: bright@wintelcom.net (Alfred Perlstein) Date: Sun, 1 Oct 2000 19:18:40 -0700 (PDT) Cc: cgaff@flashcom.net (Corey G.), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Corey G. [001001 19:01] wrote: > > No matter what, while compiling on my AMD K62-450 I get some type of > > signal 4 error. 4.1.1 compiled fine on a PIII. Any ideas? Three weeks > > ago 4.1 STABLE compiled fine too. Is my CPU going bad or is this a CPU > > incompatibility problem? > > Something is wrong with your system, check cabling, cooling and memory. I would change that to check, in order, cooling, cpu voltage setting, memory and memory timing, power supply, and finally cabling. If you have one of the rare 2.4V 450MHz K6-2-450 they are extreamly picky about Vcore ripple, and often run very very hot and need a very large heatsink and fan to run reliably. (Check the chip, the voltage setting is ingraved in the top of it, oh, and if you don't have heat sink grease on it, GET SOME!! FYI heat sink compound should be applied in a very thin layer (You should almost be able to see through it), too much is just as bad as none.) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message