On Wed, Jan 08, 2014 at 09:20:41AM +0000, Venkatesh Murthy, HemanthX wrote: > We tried pulling this commit to our tree, we still see below errors multiple > times.
That's expected. The device disconnect causes the port to go into the Inactive state and the host *must* handle that. > Should hub_port_reset also be avoided in Inactive state. > > 7>[ 181.542976] hub 2-0:1.0: port 2 not reset yet, waiting 50ms > <7>[ 181.593907] hub 2-0:1.0: port 2 not reset yet, waiting 200ms > <7>[ 181.794881] hub 2-0:1.0: port 2 not reset yet, waiting 200ms > <7>[ 181.995826] hub 2-0:1.0: port 2 not reset yet, waiting 200ms > <7>[ 182.196746] hub 2-0:1.0: port 2 not reset yet, waiting 200ms > <7>[ 182.196766] hub 2-0:1.0: port_wait_reset: err = -16 No, it cannot be avoided. The port will remain in the Inactive state unless the USB core issues a warm port reset on the port. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
