From owner-freebsd-hackers Sat May 22 2:30:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5D80A154E3 for ; Sat, 22 May 1999 02:30:36 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA35327; Sat, 22 May 1999 10:32:18 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 22 May 1999 10:32:17 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@freebsd.org, schimken@cs.rpi.edu Subject: Re: Repeatable kernel panic for 3.2-RELEASE NFS server In-Reply-To: <199905220414.VAA69868@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 May 1999, Matthew Dillon wrote: > :> entirely contained within the current stack trace. > :All my kernels are now DDB kernels :) But since I do almost all of > :my work remotely they are DDB_UNATTENDED, and the machine I am panic-ing > :is not on the serial console server (sorry). I do have another question > :about DDB, I unstalled -STABLE as of today (from releng3.fre...) and I > :compiled the kernel with DDB, and DDB_UNATTENDED per usual. Now when I > :C-A-E to get into the debugger and type 'panic' it drops me at another > :debugging prompt. If I type panic from that I get the real thing, any ideas? > : > :My next email will hopefully have the stack trace for this panic. > :-- > :David Cross | email: crossd@cs.rpi.edu > > Panic has a counter. The first time it is called it tries to drop into the > debugger. The second time it is called it reboots the machine for real. > When you control-alt-escape, you have not yet called panic for the > first time, so when you panic manually from the DDB prompt it drops you > into the debugger again. Second time's the charm! > > Since the debugger repeats the previous command if you just > hit return, I've gotten used to simply typing > 'panic ...' I use that too :-). For the alpha, I put in a 'halt' command (also linked to remote-gdb's kill operation) which drops the machine back to the firmware which is handy if you don't care about buffers not being synced. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message