Re: BUS infrastructure problem

M. Warner Losh wrote:

>In message: <42CAAFCB.2080207_at_cronyx.ru>
>            Roman Kurakin <rik_at_cronyx.ru> writes:
>: Hi,
>: 
>: M. Warner Losh wrote:
>: 
>: >In message: <42C57523.4050302_at_cronyx.ru>
>: >            Roman Kurakin <rik_at_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.
>  
>
There is no need in debugger. The function called instead of my probe 
function is
a kobj_error_method(). I guess this is desc->deflt, but why? Loader problem?

PS. I've used kdb_enter () & __asm ("int 3") both was unsuccessful.

rik

>Warner
>_______________________________________________
>freebsd-current_at_freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>  
>