From owner-freebsd-stable@FreeBSD.ORG Fri Oct 19 22:05:15 2007 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 8A1F816A475 for ; Fri, 19 Oct 2007 22:05:15 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 8118D13C459 for ; Fri, 19 Oct 2007 22:05:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id E98FE1A4D87; Fri, 19 Oct 2007 15:05:01 -0700 (PDT) Date: Fri, 19 Oct 2007 15:05:01 -0700 From: Alfred Perlstein To: Oleg Derevenetz Message-ID: <20071019220501.GL31826@elvis.mu.org> References: <027d01c8125c$73d4db80$c8c55358@delloleg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <027d01c8125c$73d4db80$c8c55358@delloleg> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: kern/104406: [ufs] Processes get stuck in "ufs" state under persistent CPU load 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: Fri, 19 Oct 2007 22:05:15 -0000 * Oleg Derevenetz [071019 08:17] wrote: > Hi all, > > Can anyone take a look on PR kern/104406 ? I got repeatable hang situation, > but I can't obtain a kernel dump to get result of all show commands from > here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > > After my break to debugger using Ctrl+Alt+Esc sequence and entering a > "panic" command kernel does not wrote a kernel dump but seems to hang. Can > anyone describe how to obtain a kernel dump in this situation, or at least > say - which output of show commands need in first place to debug this ? > Output of all suggested commands is huge and I afraid of making mistake > when carrying this output from screen to list of paper and back :-) Oleg, one thing you can do to make this less painful is to run your machine's console over serial port. First get a crossover serial cable, make sure it works from one box to another, it should be easy to run "tip com1" on both boxes to ensure that it works. Then you just need to add console=comconsole to /boot/loader.conf and your box's console should come over serial. Then on the machine watching the console, you can just do this: % script Script started, output file is typescript % tip com1 ...do ddb stuff now... ...stop tip % exit now you should have everything logged into a file called "typescript" should save you a big headache. As far as getting a dump from ddb, try this: ddb> call doadump I'm completely at a loss why this isn't a base ddb command "dump" but whatever... :) -Alfred