From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 4 01:08:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F4E316A4CE for ; Wed, 4 Feb 2004 01:08:15 -0800 (PST) Received: from smtp2.su.se (smtp2.su.se [130.237.93.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E03B43D39 for ; Wed, 4 Feb 2004 01:08:12 -0800 (PST) (envelope-from jj@it.su.se) Received: from localhost (smtp2.su.se [127.0.0.1]) by smtp2.su.se (Postfix) with ESMTP id B55F72007AD for ; Wed, 4 Feb 2004 10:08:10 +0100 (CET) Received: from smtp2.su.se ([127.0.0.1]) by localhost (smtp2.su.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29969-12 for ; Wed, 4 Feb 2004 10:08:10 +0100 (CET) Received: from it.su.se (jj.it.su.se [130.237.95.193]) by smtp2.su.se (Postfix) with ESMTP id 9FEAC2000B1 for ; Wed, 4 Feb 2004 10:08:10 +0100 (CET) Message-ID: <4020B672.9080304@it.su.se> Date: Wed, 04 Feb 2004 10:08:02 +0100 From: Janne Johansson Organization: Stockholms Universitet User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040123 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org X-Enigmail-Version: 0.82.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at su.se Subject: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 09:08:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an amd64-3000 on a Abit motherboard, 1G ram, satadisk and it works nice enough on 32-bitmode winxp, but I can't get it to be stable in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes it crash for sure is the /usr/ports/benchmarks/ubench program. It does the cpu-test and prints those results and then when it gets to test "memory speed" in part 2, it always dies on me. Of course, other activities related to recently-installed systems makes it crash too. I thought it could have been the sk-ethernet that was the culprit, since post-installation-stuff for me includes getting bash/emacs, cvs:ing and so on and that 5.2.1RC might fix that, but the ubench program uses no network afaik. So I am wondering, is it the same for other socket754-amd64-users and what can I do? Serial console to pick up crash dumps? Turn on more verbose crash-report stuff somehow? build an even more recent kernel? Turn off smp-support (I have only one cpu) or power-saving stuff in the bios? Turn on Cool-n-quiet (some mhz-altering stuff as I gather) or move from SATA to scsi in case that would be part of the problem? Advice needed. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAILZyKWyDo3z7ubcRAn4LAJ4kue4dlTK3FbQz80nxVkugtbQFGgCeMugj usp+7qU9ZurRldIGH9sXBJ4= =+9EN -----END PGP SIGNATURE-----