From owner-freebsd-current@FreeBSD.ORG Sun Feb 20 23:11:40 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 078B816A4CE; Sun, 20 Feb 2005 23:11:40 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 396BF43D1F; Sun, 20 Feb 2005 23:11:39 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.31.188]) by lakermmtao08.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050220231137.QBUP5415.lakermmtao08.cox.net@dolphin.local.net>; Sun, 20 Feb 2005 18:11:37 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.3/8.13.3) with ESMTP id j1KNBXQF001005; Sun, 20 Feb 2005 17:11:33 -0600 (CST) (envelope-from conrads@cox.net) Date: Sun, 20 Feb 2005 17:11:28 -0600 From: "Conrad J. Sabatier" To: David Xu Message-ID: <20050220171128.7d1e917e@dolphin.local.net> In-Reply-To: <421808E9.8060706@freebsd.org> References: <421808E9.8060706@freebsd.org> X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: AMD64 machine stability problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 20 Feb 2005 23:11:40 -0000 On Sun, 20 Feb 2005 11:50:01 +0800, David Xu wrote: > Did anyone encounter stability problem ? I am running X11 on it, > and sometimes it suddenly reboots. I hope it is not a mobo problem. No reboots here, but panics and freezes, yes. I suspect it has to do with NFS (at least in my case), as the problem occurs anytime my two machines' NFS mounts get out of step with each other (due to reboots or whatever). I've reverted to using a kernel from Sunday, Feb. 13 for the time being. All recent attempts to use newer kernels result in the same problem. -- Conrad J. Sabatier -- "In Unix veritas"