On Wed, Nov 16, 2016 at 06:56:30PM +0800, Kai-Heng Feng wrote: > On Wed, Nov 16, 2016 at 6:47 PM, Greg KH <greg@xxxxxxxxx> wrote: > > On Wed, Nov 16, 2016 at 06:42:27PM +0800, Kai-Heng Feng wrote: > >> Originally I sent a not-working patch to the mailing list [1], turns > >> out the patch is far from correct. > >> > >> Bjørn Mork suggests that we can cover the USB3 pair diff pins with > >> tape to do some experiment, but the vendor told me that there's no > >> such pin. > >> > >> According to the attached log, looks like xhci driver failed to get > >> status from port after resume, eventually make the cdc_mbim probe > >> failed: > >> > >> [ 10.038428] xhci_hcd 0000:00:14.0: get port status, actual port 1 > >> status = 0x202c0 > >> [ 10.038429] xhci_hcd 0000:00:14.0: Get port status returned 0x102c0 > >> [ 10.038463] usb usb2-port2: status 0001.02c0 after resume, -19 > >> [ 10.038465] usb 2-2: can't resume, status -19 > >> [ 10.038465] usb usb2-port2: logical disconnect > >> [ 10.038472] xhci_hcd 0000:00:14.0: Cannot set link state. > > > > Odd. What kernel version is this? > > > > xhci/for-usb-next branch: > 6005a545cadb2adca64350c7aee17d002563e8c7 usb: hub: Fix auto-remount of > safely removed or ejected USB-3 devices > > The latest mainline tag in this branch is 4.9-rc3. Ah, then you might want to cc: the maintainer of that branch... -- 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
