From owner-freebsd-current@FreeBSD.ORG Sat Sep 8 15:05:09 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DD0116A417; Sat, 8 Sep 2007 15:05:09 +0000 (UTC) (envelope-from bsd-current@epcdirect.co.uk) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.freebsd.org (Postfix) with ESMTP id 2BC8113C45A; Sat, 8 Sep 2007 15:05:09 +0000 (UTC) (envelope-from bsd-current@epcdirect.co.uk) Received: from localhost (localhost.epcdirect.co.uk [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 2E50E617C; Sat, 8 Sep 2007 16:05:08 +0100 (BST) X-Virus-Scanned: by GunFright.EPCDirect.co.uk Received: from gunfright.epcdirect.co.uk ([127.0.0.1]) by localhost (gunfright.epcdirect.co.uk [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id srFknU49DNj6; Sat, 8 Sep 2007 16:05:07 +0100 (BST) Received: from lfarr (lfarr.adsl.gemsoft.co.uk [195.10.239.114]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 576EB6176; Sat, 8 Sep 2007 16:05:05 +0100 (BST) From: "Lawrence Farr" To: "'Danny Braniss'" References: <20070904233246.GA2409@epia-2.farid-hajji.net> <043a01c7f202$a7ad0920$f7071b60$@co.uk> In-Reply-To: Date: Sat, 8 Sep 2007 16:05:03 +0100 Message-ID: <046801c7f229$a4534510$ecf9cf30$@co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcfyJjcSRld9Kgw+Rhanj/p+P4ULaQAA0OMw Content-Language: en-gb Cc: freebsd-current@FreeBSD.org, 'cpghost' , 'Gavin Atkinson' Subject: RE: dump problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 08 Sep 2007 15:05:09 -0000 > > the only indication I can see, is that one of the dump procs. is > waiting on > sbwait, and probably it's some deadlock, which is similar to what I > keep > seeing here, i'll try now with SCHED_ULE to see if it make a > difference. I'm running SCHED_ULE on these already, if your not I guess it's not the scheduler?