From owner-freebsd-current@FreeBSD.ORG Wed Jun 17 21:07:53 2009 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 C43A010656D2 for ; Wed, 17 Jun 2009 21:07:53 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-out2.uni-muenster.de (ZIVM-OUT2.UNI-MUENSTER.DE [128.176.192.9]) by mx1.freebsd.org (Postfix) with ESMTP id 58A4F8FC13 for ; Wed, 17 Jun 2009 21:07:52 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) X-IronPort-AV: E=Sophos;i="4.42,239,1243807200"; d="scan'208";a="216427744" Received: from zivmaildisp2.uni-muenster.de (HELO ZIVMAILUSER03.UNI-MUENSTER.DE) ([128.176.188.143]) by zivm-relay2.uni-muenster.de with ESMTP; 17 Jun 2009 23:07:51 +0200 Received: by ZIVMAILUSER03.UNI-MUENSTER.DE (Postfix, from userid 149459) id 7321D1B075E; Wed, 17 Jun 2009 23:07:51 +0200 (CEST) Date: Wed, 17 Jun 2009 23:07:50 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: debug.debugger_on_panic = 0 yet still entering db 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: Wed, 17 Jun 2009 21:07:54 -0000 i'd like to get a bt from a panic which occurs after doing `acpiconf -s 3`. since i'm using a usb keyboard (which doesn't work in db) i've set debug.debugger_on_panic = 0 ("options KDB_UNATTENDED" in kernel). yet when the panic occurs freebsd still enters the debugger! i also get another panic which is virtualbox related, but when the virtualbox related panic occurs the core gets dumped and freebsd reboots as it should do. since i cannot use my usb keyboard when the acpi panic occurs i don't know what kind of panic this is, but i think it saw the term "spinlock". i'm running r194284. this is the output of `sysctl -a|grep panic`: kern.sync_on_panic: 0 debug.ddb.textdump.do_panic: 1 debug.trace_on_panic: 1 debug.debugger_on_panic: 0 debug.kdb.panic: 0 machdep.enable_panic_key: 0 machdep.panic_on_nmi: 1 cheers.