On Sun, 25 Apr 2004, Jan Capek wrote: > Speaking of 2.4 or 2.6 kernel? I saw this issue in my 2.6 kernel using > this driver. It doesn't seem to have any impact. Any input from anyone who > is working on the relevant part of the USB layer?
That sort of thing is normal under some circumstances with 2.6. When a device is disconnected or a driver is unloaded, all its URBs are automatically unlinked by the USB core before the disconnect() routine is run. Hence the driver's own calls to usb_unlink_urb() get errors. This doesn't happen when the device file is closed, if the driver remains bound to the device. So if these errors occur every time you close the port, then most likely something is wrong. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
