On Tue, Dec 09, 2003 at 11:49:27AM +0100, Duncan Sands wrote:
> > I didn't note the reason for the oops. Was it a segmentation violation?
> > The usb_device memory isn't deallocated until the reference count goes to
> > 0. Maybe something was doing an extra usb_put_dev.
>
> Maybe this is related to "oopses in kobjects in 2.6.0-test11 (was Re: kobject
> patch)"?
> My call to usb_put_dev in usbdev_release is releasing the kobject,
> which shows that the reference count was not already zero. However
> it dereferences a NULL pointer in here:
>
> static void hcd_pci_release(struct usb_bus *bus)
> {
> struct usb_hcd *hcd = bus->hcpriv;
>
> if (hcd)
> hcd->driver->hcd_free(hcd);
> }
>
> which suggests that the hcd was already released. Maybe Greg can comment?
Does not look like the kobject oops. This looks like something else is
messing up the hcd pointer.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
