Messages in this thread | | | Date | Fri, 5 Dec 2003 15:36:18 -0800 | From | Greg KH <> | Subject | Re: Oops w/sysfs when closing a disconnected usb serial device |
| |
On Tue, Dec 02, 2003 at 12:41:13PM +0530, Maneesh Soni wrote: > Hi Mike, > > I think now I understand the problem better. It looks to me a case of > parent kobject going away before child.
Yes, but I don't see how that is happening in the usb code :(
> As we have > > > sysfs 1-1: removing dir > > o 1-1:1.0 (10): <7>removing<7> done > > and then > > sysfs 1-1:1.0: removing dir > > Its good that you enabled debug printks. We can see error > > > usb 1-1: hcd_unlink_urb d3d33f60 fail -22
This isn't an error, it can be ignored. It just means that the driver told the usb core to unlink a urb that was already unlinked. Very common thing.
> I think Greg or Pat can help you better in this case. I have no idea if > this error is creating this problem.
It's not this error, but something else. The usb-serial code hasn't changed in a while. Can you try figuring out what kernel version this bug shows up in?
thanks,
greg k-h - 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/
| |