From owner-freebsd-current@FreeBSD.ORG Fri May 7 08:29:02 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 3A05D16A4CE; Fri, 7 May 2004 08:29:02 -0700 (PDT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE39643D46; Fri, 7 May 2004 08:29:01 -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 1BM7HX-0004ZZ-00; Fri, 07 May 2004 17:28:59 +0200 To: Brian Fundakowski Feldman From: Ian FREISLICH In-Reply-To: Message from Brian Fundakowski Feldman <200405071449.i47En37w016863@green.homeunix.org> Date: Fri, 07 May 2004 17:28:59 +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: Fri, 07 May 2004 15:29:02 -0000 > 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. I'll get these the next time it does this. The kernel is compile without DDB, so I hope it's not a heisenbug. Ian -- Ian Freislich