From owner-freebsd-stable@FreeBSD.ORG Thu Feb 26 21:48:47 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 2B755106564A for ; Thu, 26 Feb 2009 21:48:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id F02478FC15 for ; Thu, 26 Feb 2009 21:48:46 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net [98.109.39.197]) by cyrus.watson.org (Postfix) with ESMTPSA id 8822A46BA5; Thu, 26 Feb 2009 16:48:46 -0500 (EST) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n1QLme6N045657; Thu, 26 Feb 2009 16:48:40 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Guy Helmer Date: Thu, 26 Feb 2009 16:48:32 -0500 User-Agent: KMail/1.9.7 References: <49A46AB4.3080003@palisadesys.com> <200902261012.24325.jhb@freebsd.org> <49A70807.9020600@palisadesys.com> In-Reply-To: <49A70807.9020600@palisadesys.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902261648.32845.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 26 Feb 2009 16:48:40 -0500 (EST) X-Virus-Scanned: ClamAV 0.94.2/9051/Thu Feb 26 08:08:01 2009 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx 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: Thu, 26 Feb 2009 21:48:47 -0000 On Thursday 26 February 2009 4:22:15 pm Guy Helmer wrote: > db> show sleepchain 23110 > thread 100181 (pid 23110, vmstat) blocked on sx "user map" XLOCK > thread 100208 (pid 23092, kvoop) is on a run queue > db> show sleepchain 23092 > thread 100208 (pid 23092, kvoop) is on a run queue Ah, so this is normal (well, mostly) in that kvoop is simply on the run queue waiting for a CPU. Can you find the thread pointer for kvoop and check on things such as if it is pinned and if so to which CPU (td_pinned will tell you the first, and td_sched->ts_cpu will tell you the second with ULE). Then you will want to see what is running on that CPU. You might want to check your other coredump and find the td_state member of the thread for kvoop there as well. -- John Baldwin