From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:58:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2600E16A41A for ; Mon, 24 Sep 2007 17:58:22 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id F375F13C481 for ; Mon, 24 Sep 2007 17:58:21 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: by muon.bluestop.org (Postfix, from userid 1000) id 634BD301F6; Mon, 24 Sep 2007 18:32:21 +0100 (BST) Date: Mon, 24 Sep 2007 18:32:21 +0100 From: bruce@cran.org.uk To: "P.U.Kruppa" Message-ID: <20070924173221.GA18292@muon.bluestop.org> References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> <20070924114923.C10251@small> <20070924100607.GC1462@elvandar.org> <20070924183258.J1576@small> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070924183258.J1576@small> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Remko Lodder , freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 24 Sep 2007 17:58:22 -0000 On Mon, Sep 24, 2007 at 06:36:53PM +0200, P.U.Kruppa wrote: > Sorry, from developer's handbook I guess I should find a vmcore.N > file. There isn't any. My parallel printing attempts end up in > some kind of single user mode on the root terminal with a > db> > prompt. Can I do anything with that? > That's the DDB prompt: from there you need to either get a backtrace or, more usefully, generate a crash dump. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html for details. To generate a crash dump that you can later use with kgdb, type "panic" at the db> prompt. Then, read http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html to find out how to obtain a backtrace that can help diagnose the fault. If using the "panic" command doesn't generate a crash dump, you could also do some diagnostics at the db> prompt by using commands such as "trace" to get a stack trace, but unless you're connected over serial you won't be able to get a copy of the output so it's better to see if you can generate a crash dump first. -- Bruce