From owner-freebsd-amd64@FreeBSD.ORG  Wed May 25 22:09:28 2005
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: amd64@freebsd.org
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 2322E16A41C
	for <amd64@freebsd.org>; Wed, 25 May 2005 22:09:28 +0000 (GMT)
	(envelope-from kometen@gmail.com)
Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BC4CA43D49
	for <amd64@freebsd.org>; Wed, 25 May 2005 22:09:27 +0000 (GMT)
	(envelope-from kometen@gmail.com)
Received: by rproxy.gmail.com with SMTP id a41so161265rng
	for <amd64@freebsd.org>; Wed, 25 May 2005 15:09:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=WtzR1EBcriXGR2mpeqUpyRyw51c+6QjThWvYaV3n1a8zdS+EI2aBsz6CvyXeI16Tx3cl5J9CPBpQLofCpG28yP6nW+xmSTNOWloPR3sYAvstMpVt58nhmaaaBkvzaoRWzV6FRTB5QJ6HspMwIKoDBtj5KwkGKNKslfInPCRgaP0=
Received: by 10.38.74.75 with SMTP id w75mr1319931rna;
	Wed, 25 May 2005 15:09:26 -0700 (PDT)
Received: by 10.38.149.57 with HTTP; Wed, 25 May 2005 15:09:26 -0700 (PDT)
Message-ID: <b41c7552050525150911915bf6@mail.gmail.com>
Date: Thu, 26 May 2005 00:09:26 +0200
From: Claus Guttesen <kometen@gmail.com>
To: Palle Girgensohn <girgen@pingpong.net>
In-Reply-To: <75f1b24e6dc7e145f7d36a874b825ab1@pingpong.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <75f1b24e6dc7e145f7d36a874b825ab1@pingpong.net>
Cc: amd64@freebsd.org
Subject: Re: Dual Xeon EM64T crashes reliably w/ 5.x amd64
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Claus Guttesen <kometen@gmail.com>
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2005 22:09:28 -0000

> with identical hardware. His machine is not as loaded, so in his case
> moving from four CPUs (two "real" + HTT) to two real (shutting down
> HTT) was enough to stop the crashes. For me, I must run UP.

What compile-options do you have in /etc/make.conf? Doing php I guess
it's a web-server, what other apps are running on the server? Is the
server located in a location with adequate cooling?

May not apply any longer, but during the 5.1-days Scott Long advised
me to add the following lines to /boot/loader.conf:

echo vm.kmem_size=3D"450000000" >> /boot/loader.conf
echo kern.maxvnodes=3D"200000" >> /boot/loader.conf

That prevented my webservers from rebooting without any apparent
reason. Too many temp-files was the cause. Try purging temp-files more
often if the above lines do help.

Claus