On Mon, Jan 09, 2017 at 11:08:39AM +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 09, 2017 at 10:51:34AM +0100, Patrice Chotard wrote: > > Hi Mathias, Greg > > > > I am working on ARM STi platform, since v4.10-rc1, when booting B2260 or B2120 STi boards platform > > with nothing plugged on USB3 connector, i observed the following kernel logs : > > > > .... > > [ 801.953836] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? > > [ 801.960455] xhci-hcd xhci-hcd.0.auto: Cannot set link state. > > [ 801.966611] usb usb6-port1: cannot disable (err = -32) > > [ 806.083772] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? > > [ 806.090370] xhci-hcd xhci-hcd.0.auto: Cannot set link state. > > [ 806.096494] usb usb6-port1: cannot disable (err = -32) > > [ 810.208766] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? > > [ 810.215374] xhci-hcd xhci-hcd.0.auto: Cannot set link state. > > [ 810.221478] usb usb6-port1: cannot disable (err = -32) > > [ 814.333767] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? > > [ 814.340364] xhci-hcd xhci-hcd.0.auto: Cannot set link state. > > ..... > > > > Another interesting thing is even if i plugged a device (a mass storage device in my case) on the USB3 connector, > > the above logs continue to appear. > > > > This is due to commit 37be66767e3ca "usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices". > > > > I don't know if STi platforms are the only impacted by this issue. > > > > On v4.9 everything was ok. > > Can you try 4.10-rc3? A bunch of xhci fixes just landed there. > > If that doesn't work, can you bisect between 4.9 and 4.10-rc1 to find > the offending commit? Oh nevermind you point that out right here :) Try 4.10-rc3 first though, that would be good to know. thanks, greg k-h -- 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
