Date: Tue, 27 Jul 2004 15:30:17 +0200 (CEST) From: Peter Holm <peter@holm.cc> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/69663: ddb's panic comand can not dump Message-ID: <200407271330.i6RDUHq2000763@current.osted.lan> Resent-Message-ID: <200407271340.i6RDeMuG071358@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 69663 >Category: kern >Synopsis: ddb's panic comand can not dump >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 27 13:40:22 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Peter Holm >Release: FreeBSD 5.2-CURRENT i386 >Organization: >Environment: System: FreeBSD current.osted.lan 5.2-CURRENT FreeBSD 5.2-CURRENT #11: Tue Jul 27 13:33:59 CEST 2004 pho@current.osted.lan:/usr/src/sys/i386/compile/PHO i386 >Description: When the ddb comand 'panic' is used, the kernel is stuck in kern/kern_shutdown.c:389 EVENTHANDLER_INVOKE(shutdown_post_sync, howto); and no dump is generated. KDB: enter: manual escape to debugger [thread 100005] Stopped at kdb_enter+0x30: movl %ebp,%esp db> panic panic: from debugger cpuid = 0; Uptime: 26s >How-To-Repeat: Call panic from ddb. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407271330.i6RDUHq2000763>