On Wed, 6 Nov 2013, Julius Werner wrote: > This patch adds a check for USB_STATE_NOTATTACHED to the > hub_port_warm_reset_required() workaround for ports that end up in > Compliance Mode in hub_events() when trying to decide which reset > function to use. Trying to call usb_reset_device() with a NOTATTACHED > device will just fail and leave the port broken. What if the device is in USB_STATE_SUSPENDED? > > Also bumped the messages about this kind of reset failure from dev_dbg() > to dev_warn() to make it easier to notice, since calling that function > with a NOTATTACHED device would almost always be a bug Not at all. If a device is unplugged, its state changes to NOTATTACHED before the driver is unbound. During that time, the driver will see all its URBs failing, so it may very well try to reset the device. (For example, usbhid behaves like this.) That isn't a bug. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
