From owner-freebsd-stable@FreeBSD.ORG Tue May 17 20:40:38 2005 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 3939F16A4CE for ; Tue, 17 May 2005 20:40:38 +0000 (GMT) Received: from mail28.syd.optusnet.com.au (mail28.syd.optusnet.com.au [211.29.133.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B7FC43D66 for ; Tue, 17 May 2005 20:40:37 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j4HKeUlg009199 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 18 May 2005 06:40:30 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j4HKeURx001669; Wed, 18 May 2005 06:40:30 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j4HKeTU9001668; Wed, 18 May 2005 06:40:29 +1000 (EST) (envelope-from pjeremy) Date: Wed, 18 May 2005 06:40:29 +1000 From: Peter Jeremy To: Brent Casavant Message-ID: <20050517204029.GC1511@cirb503493.alcatel.com.au> References: <20050517062002.465BE16A4E3@hub.freebsd.org> <20050517095122.W2946@chenjesu.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050517095122.W2946@chenjesu.americas.sgi.com> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RC2 freezing - ATA related? 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: Tue, 17 May 2005 20:40:38 -0000 On Tue, 2005-May-17 09:58:33 -0500, Brent Casavant wrote: >The only solution I found at that time was reverting to 4.10, though >that is obviously suboptimal. I could be persuaded to reinstall 5.x >on the machine if I'd be sure to get someone to look into this. It doesn't work that way. You are going to need to provide much more information and do some of the work yourself. I'd suggest that you: 1) Install 5.4-RELEASE (or -STABLE), including a kernel built with debugging and DDB enabled (see my previous post and/or the handbook). 2) Confirm that the problem still exists for you. 3) Since you think it's the daily tasks, run "periodic daily" manually and try to provoke the problem. 4) Once you can provoke it, run the scripts in /etc/periodic/daily individually to identify which script is the problem. Try to narrow it down to a single command within the script. 5) Once you can identify a command (or command sequence) that provokes' the problem, save a crashdump and send your dmesg, the sequence of commands you ran as well as the DDB output from "show lockedvnods" and "ps" to this list. That's enough information for someone to make a start on investigating the problem. If that's all too hard and you want a fix, see http://www.freebsd.org/commercial/consult_bycat.html -- Peter Jeremy