From owner-freebsd-stable@FreeBSD.ORG Fri Dec 10 00:50:19 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADF7916A4CE for ; Fri, 10 Dec 2004 00:50:19 +0000 (GMT) Received: from mscan1.cs.kent.edu (mscan1.cs.kent.edu [131.123.35.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0295543D5F for ; Fri, 10 Dec 2004 00:50:19 +0000 (GMT) (envelope-from astephan@cs.kent.edu) Received: from localhost (localhost.localdomain [127.0.0.1]) by mscan1.cs.kent.edu (8.12.10/8.12.10) with ESMTP id iBA0oC1N007882; Thu, 9 Dec 2004 19:50:12 -0500 Received: from mscan1.cs.kent.edu ([127.0.0.1]) by localhost (mscan1.cs.kent.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 07561-06; Thu, 9 Dec 2004 19:50:10 -0500 (EST) Received: from [192.168.1.25] (host-202-215-38-65-adsl8.svips.gol.ne.jp [202.215.38.65]) (authenticated bits=0) by mscan1.cs.kent.edu (8.12.10/8.12.10) with ESMTP id iBA0o5dC007874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 19:50:09 -0500 Message-ID: <41B8F343.1020308@cs.kent.edu> Date: Fri, 10 Dec 2004 09:52:19 +0900 From: Aaron Stephanic User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040811) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cs.kent.edu Subject: freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 00:50:19 -0000 I've had a server freeze three times on me know and I have no idea what the problem is... of course nothing gets output to the logs. The first time it was at 3AM on a Sunday so I thought the problem must be one of the periodic scripts. But those seemed fine when run by hand. The second two times it was just after 11PM on a Thursday. Does anyone know what could be running at that time? This is a dual Xeon machine and the kernel and world were compiled with a pentium4 CPUTYPE, but I thought that could be the problem so the last time it froze I recompiled everything for i686. But it froze again. There are still some installed ports compiled for pentium4. Now I'm thinking it could be PAE. I'm using the PAE config file that ships with 5.3 with a few extra settings. I think I'm going to disable that. Is there any way I can get more information if/when it freezes next time? Thanks. Aaron Stephanic