On 08/20/2012 08:53 AM, VIKAS SAJJAN C wrote:
After this 3.0 port becomes DEAD, it does not detect any attach /detach.
even i tired with another hub, same is the issue...
all the cases of suspend / resume works except this case, by that i mean
1. USB 3.0 Device on 3.0 port - Works fine.
2. USB 3.0 Device on 2.0 port - Works fine.
3. USB 2.0 Device on 3.0 port - Works fine.
4. USB 2.0 Device on 2.0 port - Works fine.
5. USB 2.0 Device on SS hub on 3.0 port - Works fine.
6. USB 2.0 Device on 2.0 hub on 3.0 port - Works fine.
7. USB 3.0 Device on 2.0 hub on 3.0 port - Works fine.
8. USB 3.0 Device on SS hub on 2.0 port - Works fine.
9. USB 3.0 Device on SS hub on 3.0 port - FAILS.
Reading your mails it seems to me you have the same issue as I do. I
have a problem with bluetooth device connected to usb3 port and I get
same errors in dmesg about device not accepting address. Also after
suspend/hibernate device seems to be 'dead'.
http://www.spinics.net/lists/linux-usb/msg69223.html
--
Best regards,
Miroslav
--
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
