From owner-freebsd-current@FreeBSD.ORG Wed Oct 19 15:30:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE71E16A41F for ; Wed, 19 Oct 2005 15:30:50 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A73043D48 for ; Wed, 19 Oct 2005 15:30:50 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9JFScaP068237; Wed, 19 Oct 2005 09:28:38 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 19 Oct 2005 09:29:57 -0600 (MDT) Message-Id: <20051019.092957.122315513.imp@bsdimp.com> To: info@martenvijn.nl From: "M. Warner Losh" In-Reply-To: <1129735927.689.37.camel@localhost.localdomain> References: <1129663158.715.35.camel@localhost.localdomain> <20051018.170403.10821844.imp@bsdimp.com> <1129735927.689.37.camel@localhost.localdomain> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 19 Oct 2005 09:28:38 -0600 (MDT) Cc: freebsd-current@freebsd.org Subject: Re: cf-card in pccard slot panics kernel 6.0 BETA and rc1 at boottime 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, 19 Oct 2005 15:30:50 -0000 In message: <1129735927.689.37.camel@localhost.localdomain> Marten Vijn writes: : On Tue, 2005-10-18 at 17:04 -0600, M. Warner Losh wrote: : : 1 ==> Maybe you could also try: : > : > On Sat, 2005-10-15 at 22:21 -0600, M. Warner Losh wrote: : > ...> Please consider applying the following patch. : > : > and see if that changes anything... : : With or without the patch there is no difference. : : : 2 ==> : > Any chance for a trace? Without it, this is impossible to make : > progress on since it doesn't happen for me here... : : Yes, I would like but I don't know how jet. : : added for debugging to my kernelconfig: : : options KTR : options KTR_ENTRIES=1024 : options KTR_VERBOSE : options KTR_ALQ Actually you need the following: # # Compile with kernel debugger related code. # options KDB # # Enable the ddb debugger backend. # options DDB and when the panic happens, you'll get 'db> ' prompt. Type 'trace' there and report what comes back. Warner