* Greg KH <gregkh@suse.de> wrote:

quoted text
> > Device 'fixed@10:1' does not have a release() function, it is broken and must be fixed.
> > BUG: at drivers/base/core.c:120 device_release()
> >  [<c0105ff9>] show_trace_log_lvl+0x19/0x2e
> >  [<c01063e2>] show_trace+0x12/0x14
> >  [<c01063f8>] dump_stack+0x14/0x16
> >  [<c063cddf>] device_release+0x7c/0x7e
> >  [<c0476c32>] kobject_cleanup+0x44/0x5e
> >  [<c0476c57>] kobject_release+0xb/0xd
> >  [<c04773ef>] kref_put+0x63/0x71
> >  [<c0476757>] kobject_put+0x14/0x16
> >  [<c063ceef>] put_device+0x11/0x13
> >  [<c063d943>] device_unregister+0x12/0x15
> >  [<c07337d1>] fixed_mdio_register_device+0x210/0x23b
> >  [<c1b6d6c1>] fixed_init+0x2f/0x33
> >  [<c1b31a2d>] init+0x15d/0x2bd
> >  [<c0105bc3>] kernel_thread_helper+0x7/0x10
> 
> That means that whatever driver has fixed_mdio_register_device() in it 
> is broken and needs to be fixed.

that would be drivers/net/phy/fixed.c.

quoted text
> It is independant from your previous question about unregistering the 
> device from within module_init().

(yes - hence the different subject line, etc.)

	Ingo
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/