From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 08:13:27 2004 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 1059116A4CE for ; Mon, 8 Mar 2004 08:13:27 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C260A43D31 for ; Mon, 8 Mar 2004 08:13:25 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i28GBwxC018873; Mon, 8 Mar 2004 11:11:58 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i28GBwcd018870; Mon, 8 Mar 2004 11:11:58 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 8 Mar 2004 11:11:57 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Scott Sipe In-Reply-To: <404BC906.90905@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Crashing under NFS load 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: Mon, 08 Mar 2004 16:13:27 -0000 On Sun, 7 Mar 2004, Scott Sipe wrote: > I have one box running CURRENT from Feb 29. It is a headless box, and > acts as an NFS server sreving up /usr/src and /usr/obj for my laptop. > Three times now, I have been doing something on the laptop (buildworld, > most recently I just did an "installkernel") and the headless NFS server > stops working, and resets--it comes back up fine, and the nfs client > resumes normally. > > I've found nothing in any /var/log files that sheds a clue. > > Is there anything I can do to identify the problem? I'm in the process > of updating to the latest current to see if that fixes it. Well, it would be fascinating to know if in that period between when it goes offline, and comes back up, the console is actually outputting a panic message. Could you hook up a serial console, or turn on crashdumps, if they're not already on? Silent reboots are hard to debug, but panics followed by reboots are a lot easier. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research