From owner-freebsd-bugs@FreeBSD.ORG Tue Oct 23 10:00:04 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35FAA16A421 for ; Tue, 23 Oct 2007 10:00:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 42F1013C4B6 for ; Tue, 23 Oct 2007 10:00:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l9NA03jk055583 for ; Tue, 23 Oct 2007 10:00:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l9NA03hm055576; Tue, 23 Oct 2007 10:00:03 GMT (envelope-from gnats) Date: Tue, 23 Oct 2007 10:00:03 GMT Message-Id: <200710231000.l9NA03hm055576@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kostik Belousov Cc: Subject: Re: kern/104406: [ufs] Processes get stuck in "ufs" stateunderpersistent CPU load X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kostik Belousov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2007 10:00:04 -0000 The following reply was made to PR kern/104406; it has been noted by GNATS. From: Kostik Belousov To: bug-followup@FreeBSD.org Cc: Oleg Derevenetz Subject: Re: kern/104406: [ufs] Processes get stuck in "ufs" stateunderpersistent CPU load Date: Tue, 23 Oct 2007 12:54:15 +0300 --wIc/V6YLA2QdyfT4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 22, 2007 at 04:29:32PM +0400, Oleg Derevenetz wrote: > I posted a followup to kern/104406 that includes all information listed i= n=20 > "Debugging Deadlocks" chapter of FreeBSD Developer's Handbook. Can anyone= =20 > take a look on it and say - is this certainly a hardware problem or some= =20 > sort of software problem ? The ps output from ddb would simplify the analysis. The buffer space on the machine seems to be contaminated with a critical amount of the dirty buffers that are sent for the write. The pid 844 (that is the only one producing the writes) is blocked in waitrunningbufspace(), waiting for the write queue to be drained. There are other processes, for instance, 937 etc, that wait for the buffer lock. Most likely, these buffers are scheduled for write and cause the processes to be uninterruptibly blocked. If this state of the system is static, then the write queue is not processed. Most plausible cause is the controller (mly0) or the controller driver fault. --wIc/V6YLA2QdyfT4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHHcTGC3+MBN1Mb4gRAodzAKDLMJIiPnjWNRejDrnj/6R/Kic1LwCbBxK+ 9GLcje2brT6bTZA1dzB17Yg= =2chV -----END PGP SIGNATURE----- --wIc/V6YLA2QdyfT4--