From owner-freebsd-questions Tue Sep 1 15:33:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07912 for freebsd-questions-outgoing; Tue, 1 Sep 1998 15:33:32 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mbox.ualr.edu (mbox.ualr.edu [144.167.10.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07904 for ; Tue, 1 Sep 1998 15:33:30 -0700 (PDT) (envelope-from jeroyce@ualr.edu) Received: from athena.ualr.edu by UALR.EDU (PMDF V5.1-9 #24705) with SMTP id <01J1ATPN13R40017S3@UALR.EDU> for freebsd-questions@FreeBSD.ORG; Tue, 1 Sep 1998 17:32:24 CDT Received: from ualr.edu ([144.167.120.220]) by athena.ualr.edu with ESMTP for freebsd-questions@FreeBSD.ORG; Tue, 01 Sep 1998 17:32:14 -0500 Date: Tue, 01 Sep 1998 17:54:10 -0500 From: Joe Subject: Re: system crash when using 'make' To: FreeBSD Questions Message-id: <35EC7B12.5859A81A@ualr.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.5b1 [en] (Win95; I) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <199809012058.NAA23493@hub.freebsd.org> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ludwig Pummer wrote: > At 03:41 PM 9/1/98 -0500, Steve Friedrich wrote: > >I have problems on a new AMD-K6 233 (ASUS TX-97) when I make > >buildworld. But never any other time. In an attempt to isolate the > >problem, I turned off the CPUs internal and external caches. That > >allowed the buildworld to complete, though it took nearly 48hrs, > >instead of less than 24. But after make installworld, I turned the > >caches back on and I am not having any problems. It will be awhile > >before I can scrounge up the cash to buy new memory, to finish the job. > > This sounds like that cache bug that existed in the earlier K6 CPUs. The > bug showed up when doing processor intensive stuff, like compiling under > Linux, playing Wing Commander: Prophecy (the game would lock up during > missions). Turning off the CPU's internal cache fixes the problem. (i can't > find more information on it right now. i couldn't find it on AMD's web site) > > If it doesn't turn out to be the memory, maybe you should try a newer K6 chip. > > --Ludwig Pummer > ludwigp@bigfoot.com ludwigp@chipweb.ml.org > ICQ UIN: 692441 http://chipweb.home.ml.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > the website for the AMD K6 bug is http://www.mygale.org/~poulot/k6bug.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message