From owner-freebsd-questions@FreeBSD.ORG Tue Jul 27 18:03:32 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6492916A4CE for ; Tue, 27 Jul 2004 18:03:32 +0000 (GMT) Received: from orchid.homeunix.org (awb95.neoplus.adsl.tpnet.pl [83.27.61.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C4D343D5A for ; Tue, 27 Jul 2004 18:03:29 +0000 (GMT) (envelope-from freebsd@orchid.homeunix.org) Received: from [192.168.1.66] ([192.168.1.66]) (authenticated bits=0) by orchid.homeunix.org (8.12.10/8.12.10) with ESMTP id i6RI3Eu8085954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 27 Jul 2004 20:03:26 +0200 (CEST) (envelope-from freebsd@orchid.homeunix.org) Message-ID: <410698D0.7010406@orchid.homeunix.org> Date: Tue, 27 Jul 2004 20:02:56 +0200 From: Karol Kwiatkowski User-Agent: Mozilla/5.0 X-Accept-Language: en, pl, en-us MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <0E1A1C28F9D61A4D8B6F70AFA3C1B1E42831@srvw2000-cnv1.cnv.local> <38a23c360407220825778b6c68@mail.gmail.com> <4100214E.4090405@orchid.homeunix.org> <4106538D.2070506@freebsd.org> In-Reply-To: <4106538D.2070506@freebsd.org> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a on orchid.homeunix.org X-Virus-Status: Clean Subject: Re: Random Freeze X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 18:03:32 -0000 Mark Ovens wrote: > I'm seeing the same problem on my dual Athlon box. The freezes are > totally random AFAICT, sometimes when the machine is just idling. > > I've not used any CPU-specific make options but may try setting some to > see if it makes a difference. One thing though, I only have > > cpu I686_CPU > > set, not I486_CPU and I586_CPU as well, maybe that could be a problem? AFAIK, that's a proper setting for Athlons. What I recommend is you shouldn't play with make options before setting up a stable system (sorry if that's too obvious). > I'm running -CURRENT and the build I did on 8 April didn't have this > problem but it started with the next build I did a couple of weeks ago. > I've cvsup'd and rebuilt a couple of times since, the last on 25 July, > but the problem persists. I don't have much experience with CURRENT (and with SMP) but if you didn't change the config files it looks like something in the code (this is possible in CURRENT, right?). Only thing I can think of is reading freebsd-current and searching the archives. Not much from me, sorry. Regards, Karol -- Karol Kwiatkowski