On Tue, 30 Jul 2013, Sarah Sharp wrote: > On Tue, Jul 30, 2013 at 12:52:40PM -0400, Alan Stern wrote: > > Sarah, the usbmon trace shows that after doing a successful port reset > > and clearing a bunch of port features, the system tells the port to go > > into the SS.disabled state for no apparent reason: > > > > ffff88014649f3c0 1804119918 S Co:4:001:0 s 23 03 0004 0002 0000 0 > > ffff88014649f3c0 1804119924 C Co:4:001:0 0 0 > > ffff88020a1dd000 1804170382 S Ci:4:001:0 s a3 00 0000 0002 0004 4 < > > ffff88020a1dd000 1804170389 C Ci:4:001:0 0 4 = 03021000 > > ffff8801b7173300 1804221388 S Co:4:001:0 s 23 01 0014 0002 0000 0 > > ffff8801b7173300 1804221397 C Co:4:001:0 0 0 > > ffff8801b7173300 1804221398 S Co:4:001:0 s 23 01 001d 0002 0000 0 > > ffff8801b7173300 1804221403 C Co:4:001:0 0 0 > > ffff8801b7173300 1804221403 S Co:4:001:0 s 23 01 0019 0002 0000 0 > > ffff8801b7173300 1804221407 C Co:4:001:0 0 0 > > ffff8801b7173300 1804221408 S Co:4:001:0 s 23 01 0010 0002 0000 0 > > ffff8801b7173300 1804221412 C Co:4:001:0 0 0 > > ffff8801b7173300 1804221414 S Ci:4:001:0 s a3 00 0000 0002 0004 4 < > > ffff8801b7173300 1804221417 C Ci:4:001:0 0 4 = 03020000 > > ffff88014649f3c0 1804623388 S Co:4:001:0 s 23 03 0005 0402 0000 0 > > ffff88020ceb1600 1804623409 C Ii:4:001:1 0:2048 1 = 04 > > ffff88020ceb1600 1804623410 S Ii:4:001:1 -115:2048 4 < > > ffff88014649f3c0 1804623415 C Co:4:001:0 0 0 > > > > Do you have any idea why it is doing this? > > If a warm reset failed, the USB core will put the port into SS.Disabled. > If enumeration fails in the right places, the port will also be > disabled. As far as I can tell from the usbmon trace, the reset succeeded. > dmesg with CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING might help > me understand what's going on. 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
