From owner-freebsd-stable@FreeBSD.ORG Thu Apr 26 01:06:37 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BFE5616A401 for ; Thu, 26 Apr 2007 01:06:37 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id ADEA113C448 for ; Thu, 26 Apr 2007 01:06:37 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 080491A4D90; Wed, 25 Apr 2007 18:07:03 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1289D51430; Wed, 25 Apr 2007 21:06:37 -0400 (EDT) Date: Wed, 25 Apr 2007 21:06:36 -0400 From: Kris Kennaway To: Adrian Wontroba , freebsd-stable@freebsd.org Message-ID: <20070426010636.GB79851@xor.obsecurity.org> References: <20070313140848.GA89182@steerpike.hanley.stade.co.uk> <20070423025631.GA33256@steerpike.hanley.stade.co.uk> <20070426010157.GF66129@steerpike.hanley.stade.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070426010157.GF66129@steerpike.hanley.stade.co.uk> User-Agent: Mutt/1.4.2.2i Cc: Subject: Re: 6.2-STABLE deadlock? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2007 01:06:37 -0000 On Thu, Apr 26, 2007 at 02:01:57AM +0100, Adrian Wontroba wrote: > On Mon, Apr 23, 2007 at 03:56:32AM +0100, Adrian Wontroba wrote: > > Another 6-STABLE (cvsupped on 27/03/07) example, with diagnostics taken > > rather sooner after the hang. Processes with wmesg=ufs feature often in > > the ps output. > > Thanks for the assorted replies. I'll try using INVARIANTS, as I'd much > prefer a panic and automatic reboot rather than creeping death for this > server which is only attended 06:00-22:00 weekdays yet is a critical > point in our 24*7 monitoring. Sigh. Champagne tastes on a beer budget. > > Other background information (from memory as I can't access it from > here): > I'm not using unionfs / nullfs. > I am using MFS and softupdates. > NFS is in occassional use. > NTFS is not used. > The server is ancient. A 4 way Zeon, state of the art in 1998. > The problem has gone from "absent" through "reproducible if you > try hard enough" to "strikes according to Murphy" through 5.5-STABLE to > 6.2-STABLE. > > Once the sendmail milter ABI damage is fixed I'll bring the machine up > to date - it is also the build box for a dozen or so machines running > something close to 6.2-RELEASE, and I'd rather not upgrade all of them > them when the next ClamAV release appears. Fixed the other day, FYI. > If / when it hangs again, I'll include more information and maybe even > raise a real PR. Thanks. Kris