From owner-freebsd-current@FreeBSD.ORG  Tue Jul  5 22:41:46 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 7851D16A41C
	for <freebsd-current@freebsd.org>; Tue,  5 Jul 2005 22:41:46 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 37D5C43D45
	for <freebsd-current@freebsd.org>; Tue,  5 Jul 2005 22:41:46 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1])
	by harmony.village.org (8.13.3/8.13.3) with ESMTP id j65Mfbf8076756;
	Tue, 5 Jul 2005 16:41:37 -0600 (MDT) (envelope-from imp@bsdimp.com)
Date: Tue, 05 Jul 2005 16:41:35 -0600 (MDT)
Message-Id: <20050705.164135.12222348.imp@bsdimp.com>
To: rik@cronyx.ru
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <42CAAFCB.2080207@cronyx.ru>
References: <42C57523.4050302@cronyx.ru>
	<20050701.121826.56566740.imp@bsdimp.com>
	<42CAAFCB.2080207@cronyx.ru>
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
Cc: freebsd-current@freebsd.org
Subject: Re: BUS infrastructure problem
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2005 22:41:46 -0000

In message: <42CAAFCB.2080207@cronyx.ru>
            Roman Kurakin <rik@cronyx.ru> writes:
: Hi,
: 
: M. Warner Losh wrote:
: 
: >In message: <42C57523.4050302@cronyx.ru>
: >            Roman Kurakin <rik@cronyx.ru> writes:
: >:     I observe the followin strange behaviour with current: with some very
: >: high probability after indentify callback I didn't get a probe callback. I
: >: didn't find yet anything that could tell me why I see this. All function 
: >: return me that all operations was successful.
: >: 
: >: PS. This driver is cx(4) and I am currently try to debug it in async mode
: >: (I get strange panics while its work if I didn't get into situation with 
: >: probe()).
: >: 
: >: Any ideas?
: >
: >I'll be happy to help you with this.
: >  
: >
: The last place I get to is the call of DEVICE_PROBE macro.
: But I do not see the call of my function.
: There is other thing, it seems that probability highly increases
: if the system reboots after panic and needs filesystem check.
: 
: This is all information I have now. I use printf as a primary
: debug technic so I need to think how to move farther.
: 
: Ideas?

That sounds really weird.  Add a Debugger() call and see if you wind
up in the debugger.


Warner