From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 21 13:25:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 523C137B401 for ; Mon, 21 Apr 2003 13:25:51 -0700 (PDT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 921F443FD7 for ; Mon, 21 Apr 2003 13:25:50 -0700 (PDT) (envelope-from nsouch@free.fr) Received: from armor.fastether (nas-cbv-8-62-147-158-16.dial.proxad.net [62.147.158.16]) by postfix4-1.free.fr (Postfix) with SMTP id EC86F1A36B for ; Mon, 21 Apr 2003 22:25:48 +0200 (CEST) Received: (qmail 8048 invoked by uid 1001); 21 Apr 2003 22:39:25 -0000 Date: Mon, 21 Apr 2003 22:39:25 +0000 From: Nicolas Souchu To: Poul-Henning Kamp Message-ID: <20030421223925.B7928@armor.free.fr> References: <20030413223656.A21075@armor.free.fr> <3403.1050272127@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3403.1050272127@critter.freebsd.dk>; from phk@phk.freebsd.dk on Mon, Apr 14, 2003 at 12:15:27AM +0200 cc: hackers@freebsd.org Subject: Re: infinite loop in kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 20:25:51 -0000 On Mon, Apr 14, 2003 at 12:15:27AM +0200, Poul-Henning Kamp wrote: > In message <20030413223656.A21075@armor.free.fr>, Nicolas Souchu writes: > > > >Hi folks, > > > >I'm trying to debug some infinite loop in the kernel. I guess > >this is the problem since key interrupts are still working but > >the system does not respond otherwise. > > > >Unfortunatly, breaking in the debugger only gives my the > >trace of the kbd intr thread... > > > >Which data structure should I check? > > Use "ps" in DDB to see which processes are runnable for instance. Any hint on how to interpret it? The scheduler interrupts are certainly working, I could certainly break in it and see what is being currently scheduled? -- Nicholas Souchu - nsouch@free.fr - nsouch@FreeBSD.org