From owner-freebsd-current@FreeBSD.ORG Mon Jul 11 08:27:10 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 71D5316A41C for ; Mon, 11 Jul 2005 08:27:10 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89B0043D49 for ; Mon, 11 Jul 2005 08:27:09 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru (8.13.0/vak/3.0) id j6B8O4Wd066114 for freebsd-current@freebsd.org.checked; Mon, 11 Jul 2005 12:24:04 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from [144.206.181.94] (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru (8.13.0/vak/3.0) with ESMTP id j6B8LagM066077; Mon, 11 Jul 2005 12:21:36 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <42D22C1C.8070908@cronyx.ru> Date: Mon, 11 Jul 2005 12:21:48 +0400 From: Roman Kurakin User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <42C57523.4050302@cronyx.ru> <20050701.121826.56566740.imp@bsdimp.com> <42CAAFCB.2080207@cronyx.ru> <20050705.164135.12222348.imp@bsdimp.com> In-Reply-To: <20050705.164135.12222348.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2005 08:27:10 -0000 Hi, I've found the reason. It was there where I do not expect it. The only function's return value I didn't check was ... ... it was device_set_driver. It returns ENOMEM, all other stuff goes well. More over it seems that at device_probe_child () device_set_driver do not have memory problems, but driver methods table are broken. Something tells me that the call of device_set_driver from device_probe_child is intended for recovering from such case but it doesn't work. Or this is wrong guess? Do you think the case is closed or this is some misbehavior that could be fixed? rik M. Warner Losh wrote: >In message: <42CAAFCB.2080207@cronyx.ru> > Roman Kurakin writes: >: Hi, >: >: M. Warner Losh wrote: >: >: >In message: <42C57523.4050302@cronyx.ru> >: > Roman Kurakin 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 >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >