From owner-freebsd-current@FreeBSD.ORG Thu Jun 14 20:48:27 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4953E16A46C for ; Thu, 14 Jun 2007 20:48:27 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.freebsd.org (Postfix) with ESMTP id 2873813C483 for ; Thu, 14 Jun 2007 20:48:27 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn01.u.washington.edu (hymn01.u.washington.edu [140.142.8.55]) by mxout3.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l5EKmK6B026117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Jun 2007 13:48:20 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn01.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l5EKmJiH015529; Thu, 14 Jun 2007 13:48:19 -0700 X-Auth-Received: from [192.55.52.1] by hymn01.u.washington.edu via HTTP; Thu, 14 Jun 2007 13:48:19 PDT Date: Thu, 14 Jun 2007 13:48:19 -0700 (PDT) From: youshi10@u.washington.edu To: current@freebsd.org In-Reply-To: <20070614130551.E60816@10.0.0.1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.14.132733 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CP_MEDIA_2_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Jeff Roberson Subject: Re: Best way to build a "new" AMD64 current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2007 20:48:27 -0000 On Thu, 14 Jun 2007, Jeff Roberson wrote: > > On Thu, 14 Jun 2007, Walter Vaughan wrote: > >> I have a dual quad core intel box that I want to test current on. It's been >> running current about 4 weeks, and the last week has been nothing short of a >> lot of random reboots under load. But when it is running it's spectacular. >> >> (Yes I've been reading this list and UPDATING) >> >> What is the best policy to build a new current? I'll erase and start anew. >> >> I'm not much help to Jeff Roberson right now, if all the feedback is that >> regardless of the scheduler I use, it reboots under load. Sadly, I'd blame >> java in this instance, but we've gotten it to reboot more often just running >> the postgres command line tool psql with large dataset imports. > > Have you checked your BIOS event log for ram parity errors, etc? Is this the > first OS you've installed on the machine? > > You also should enable the KDB, DDB, and INVARIANTS options in your kernel to > try to catch the problem if it is a software bug. > > Thanks, > Jeff > >> >> Is this the best way? >> >> 1)Using a FreeBSD AMD64 6.2 boot only CD, and doing a minumal install. >> 2)Then installing pkg_add -r cvsup and getting the /usr/src w/ current >> 3)Then do a buildworld/kernel * install dance >> 4)Then install ports collection >> 5)Then install compat6x, postgresql, svn, javawrapper, xorglibraries >> 6)pkg_add diablo-AMD64-java-for-6.1 >> 7)svn the ERP and start testing >> >> Thanks >> -- >> Walter -What's the motherboard maker? -What's the chipset maker (nVidia, Intel)? -Have you tried out an alternate OS in testing the system? -Garrett