Date: Tue, 05 Jul 2005 16:41:35 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: rik@cronyx.ru Cc: freebsd-current@freebsd.org Subject: Re: BUS infrastructure problem Message-ID: <20050705.164135.12222348.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050705.164135.12222348.imp>