On Tue, Mar 28, 2017 at 01:45:41AM +0200, Stephan Müller wrote:
> Am Montag, 27. März 2017, 12:52:02 CEST schrieb Oliver Neukum:
>
> Hi Oliver,
>
> > Am Sonntag, den 26.03.2017, 17:31 +0200 schrieb Stephan Müller:
> > > Is there a way to reset the hub or to force a scanning the ports for
> > > potentially attached devices?
> >
> > Try adding a RESET_RESUME quirk for your device. And make sure there is
> > a medium in it. It may disconnect because it is empty.
>
> After adding the following line to drivers/usb/core/quirks.c and leaving a
> card in, the device still disconnects:
>
> { USB_DEVICE(0x05ac, 0x8406), .driver_info = USB_QUIRK_RESET_RESUME },
>
> When I compile the USB debug mode, I get the following log:
>
> [ 202.969407] *** thread awakened
> [ 202.969413] Command TEST_UNIT_READY (6 bytes)
> [ 202.969417] bytes: 00 00 00 00 00 00
> [ 202.969425] Bulk Command S 0x43425355 T 0x17e L 0 F 0 Trg 0 LUN 0 CL 6
> [ 202.969428] xfer 31 bytes
> [ 202.969435] Status code -19; transferred 13/31
> [ 202.969437] -- unknown error
> [ 202.969439] Bulk command transfer result=4
> [ 202.969443] -- transport indicates error, resetting
> [ 202.969447] unable to lock device for reset: -19
> [ 202.969454] rq=ff rqtype=21 value=0000 index=00 len=0
> [ 202.969458] Soft reset failed: -19
> [ 202.969461] scsi cmd done, result=0x70000
> [ 202.969465] *** thread sleeping
> [ 202.969530] usb 2-3: USB disconnect, device number 2
> [ 202.976878] Fail command during disconnect
> [ 202.982039] done.
>
Do you have debug information from USB core (not only USB storage)? It
may show why it is disconnected from low level.
--
Best Regards,
Peter Chen
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
