On Fri, 12 Sep 2003, Tomita, Haruo wrote: > hub.c: port 1, portstatus 110, change 3, 12 Mb/s > hub.c: port 1 connection change > hub.c: port 1, portstatus 110, change 3, 12 Mb/s > usb.c: USB disconnect on device 00:07.2-1 address 2 > usb-storage: storage_disconnect() called > usb-storage: -- releasing irq URB > usb-storage: USB IRQ received for device on host 1 > usb-storage: -- IRQ data length is 2 > usb-storage: -- IRQ state is -2 > usb-storage: -- Interrupt Status (0x0, 0x0) > usb-storage: ERROR: Unwanted interrupt received! > usb-storage: -- usb_unlink_urb() returned 0 > usb-storage: -- releasing main URB > usb-storage: -- usb_unlink_urb() returned -19 > usb.c: kusbd: /sbin/hotplug remove 2 > hub.c: port 1, portstatus 103, change 0, 12 Mb/s > usb.c: ignoring set_interface for dev 2, iface 0, alt 0 > hub.c: port 2, portstatus 100, change 0, 12 Mb/s > hub.c: port 1, portstatus 103, change 0, 12 Mb/s > hub.c: port 2, portstatus 100, change 0, 12 Mb/s
This makes it look like the device isn't probed again after usbdevfs does the port reset. Yet another thing to worry about. But since it's in 2.4, people probably won't worry about it very hard. Alan Stern ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
