From owner-freebsd-current@FreeBSD.ORG Sat May 8 02:05:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1EFA16A4CE; Sat, 8 May 2004 02:05:33 -0700 (PDT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 639CC43D41; Sat, 8 May 2004 02:05:33 -0700 (PDT) (envelope-from ianf@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 3.36 #1) id 1BMNm0-0007Yu-00; Sat, 08 May 2004 11:05:32 +0200 To: Brian Fundakowski Feldman From: Ian FREISLICH In-reply-to: Your message of "Fri, 07 May 2004 10:49:03 -0400." <200405071449.i47En37w016863@green.homeunix.org> X-Attribution: BOFH Date: Sat, 08 May 2004 11:05:31 +0200 Sender: ianf@hetzner.co.za Message-Id: cc: FreeBSD-current@freebsd.org Subject: Re: spin lock sleepq chain held by 0xc0fc3540 for > 5 seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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 May 2004 09:05:33 -0000 Brian Fundakowski Feldman wrote: > That might not be enough information to go on. Prefereably when something > like this happens, and a core dump is not going to happen, "show locks", > "ps", and "tr" of interesting processes, from DDB, would be the most useful > things to have. The debugger is not available because the system is wedged solid so these usefull data are unobtainable :( Ian -- Ian Freislich