From owner-freebsd-stable@FreeBSD.ORG Wed Feb 25 06:19:00 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57F0A106566B for ; Wed, 25 Feb 2009 06:19:00 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail2.es.net [IPv6:2001:400:107:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id E846A8FC0C for ; Wed, 25 Feb 2009 06:18:59 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n1P6IvHL020968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 24 Feb 2009 22:18:57 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4CAE21CC0B; Tue, 24 Feb 2009 22:18:57 -0800 (PST) To: Guy Helmer In-reply-to: Your message of "Tue, 24 Feb 2009 15:46:28 CST." <49A46AB4.3080003@palisadesys.com> Date: Tue, 24 Feb 2009 22:18:57 -0800 From: "Kevin Oberman" Message-Id: <20090225061857.4CAE21CC0B@ptavv.es.net> Cc: freebsd-stable@freebsd.org Subject: Re: 7.1 hangs in cache_lookup mutex? 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: Wed, 25 Feb 2009 06:19:00 -0000 > Date: Tue, 24 Feb 2009 15:46:28 -0600 > From: Guy Helmer > Sender: owner-freebsd-stable@freebsd.org > > I think I may have found a clue regarding some of the hangs I'm seeing > on FreeBSD 7.1. > I have a program (kvoop), compiled under FreeBSD 6 and using > compatibility libraries under FreeBSD 7, that seems to be consistently > involved during these hangs. This time, I noticed that many processes > are stopped, waiting on the ufs lock. I can't tell for certain, but I > assume this kvoop process 33203 is blocking the other processes. The > kvoop process looks to me like it is waiting for a mutex, but nothing > shows up being deadlocked. Am I on the right track? Is there something > else I should be looking for? For whatever it is worth, I have seen this three times over the past couple of weeks. My system is RELENG_7 of Feb. 7. I have no real information to add other than that I have also had this problem. When it happens, the only way out is a reboot. It hit me twice while updating Xorg. Thanks for your efforts! I hope someone can track down what is triggering with this. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751