Date: Tue, 26 Sep 2006 16:40:20 -0400 From: John Baldwin <jhb@freebsd.org> To: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> Cc: freebsd-stable@freebsd.org Subject: Re: Loadable SMBus modules regression in 6-STABLE -> 6-BETA Message-ID: <200609261640.20577.jhb@freebsd.org> In-Reply-To: <20060926215928.H38624@atlantis.atlantis.dp.ua> References: <20060924171559.C7094@atlantis.atlantis.dp.ua> <200609261309.19663.jhb@freebsd.org> <20060926215928.H38624@atlantis.atlantis.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 26 September 2006 15:10, Dmitry Pryanishnikov wrote:
>
> Hello!
>
> On Tue, 26 Sep 2006, John Baldwin wrote:
> > It still works here. Since you are using modules, make sure all your
modules
> > are in sync. Short of that, you can edit sys/dev/smbus/smb.c and add a
>
> Yes, they are (I've followed the standard OS upgrade procedure, including
> full recompile of the kernel and all modules).
>
> > printf to smb_identify() and make sure it is called.
>
> I've instrumented it in the following fashion:
>
> smb_identify(driver_t *driver, device_t parent)
> {
> printf("smb_identify() called!!!\n");
> if (device_find_child(parent, "smb", -1) == NULL) {
> printf("BUS_ADD_CHILD() = %p\n",
> BUS_ADD_CHILD(parent, 0, "smb", -1));
> }
> }
>
> and here is the output:
>
> smb_identify() called!!!
> BUS_ADD_CHILD() = 0x6
>
> 6? ENXIO? Why?!
I've just found it and fixed it if you upgrade to the newest smbus.c.
--
John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609261640.20577.jhb>