From owner-freebsd-current Mon Feb 10 09:27:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA13134 for current-outgoing; Mon, 10 Feb 1997 09:27:06 -0800 (PST) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA13129 for ; Mon, 10 Feb 1997 09:27:04 -0800 (PST) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id JAA09083; Mon, 10 Feb 1997 09:22:10 -0800 Date: Mon, 10 Feb 1997 09:22:10 -0800 From: Jim Shankland Message-Id: <199702101722.JAA09083@saguaro.flyingfox.com> To: andrew@why.whine.com Subject: Re: Make world of Current dies with weird errors. Cc: current@freebsd.org, phk@critter.dk.tfs.com Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I was able to actually make world today. I had been overclocking my cpu > at a 75mhz bus vs. a 66mhz bus. Dropping it to 66, or disabling the > level2 cache cause the problem to go away. Question is... why is the only > thing affected is make world? It doesn't make sense. This stuff happens. Back in the Dawn of Time, I was helping a colleague debug a problem in a full-screen text editor he was developing. Every time he issued the command to move point to a specific line number, point moved to the end of the file. Other than that, everything (everything!) worked fine. It turned out that his system was running one of the new, 6 MHz Z80 CPUs, and if you hit the CPU chip with a blast of freon, the problem disappeared for a few minutes. Hardware problems can manifest in some really weird ways, and overclocking should be done only by those who have much more time than money. Jim Shankland Flying Fox Computer Systems, Inc.