Linux USB
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: James Dutton <james.dutton@gmail.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: USB disk disconnect problems
Date: Mon, 3 Oct 2022 14:17:44 -0400	[thread overview]
Message-ID: <YzsnSPEfBesJRr9R@rowland.harvard.edu> (raw)
In-Reply-To: <CAAMvbhEV_ssOwsWU-37pauDSfM3Ekv2mrKWTjCP0vov84dMDMQ@mail.gmail.com>

On Mon, Oct 03, 2022 at 07:04:05PM +0100, James Dutton wrote:
> I have done some more tests.
> With the device plugged in, and me manually send a command to reset
> the USB device.
> Using instructions listed here:
> https://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line
> 
> The reset fails.
> It never recovers.
> So, I think there is some problem relating to USB 3.x reset, and maybe
> just my specific device which is an NVME storage in a USB dock.
> I think the problem is more to do with the Linux kernel's USB 3.x
> reset procedure, rather than any other cause.
> Is there any quirk or test I can add, that would remove power from the
> USB port and return it, as part of the reset procedure?
> Or, is there any extra debug logging I can enable to help diagnose
> where the reset function is failing?

You can try collecting a usbmon trace of the reset (instructions on the 
web or in Documentation/usb/usbmon.rst in the kernel source).  That will 
provide some clues as to whether the problem lies in the reset itself or 
in the activities that follow the reset.

Have you tried running a similar test using, say, a plain old USB thumb 
drive in place of the NVME storage device?

Alan Stern

  reply	other threads:[~2022-10-03 18:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 11:17 USB disk disconnect problems James Dutton
2022-08-21 14:47 ` Alan Stern
2022-08-21 16:36   ` James Dutton
2022-08-21 16:40     ` James Dutton
2022-08-21 18:11       ` Alan Stern
     [not found]   ` <CAA6KcBC2wEc78fgrMLBfbyEinR3rVUY6z8HeUbE=wtv0c4BP2Q@mail.gmail.com>
2022-08-21 19:03     ` Alan Stern
2022-08-21 20:03   ` Matthew Dharm
2022-08-21 20:59     ` James Dutton
2022-08-21 21:26       ` Matthew Dharm
2022-08-21 22:56         ` James Dutton
2022-08-22 10:03           ` Oliver Neukum
2022-08-22 10:18       ` Oliver Neukum
2022-10-03 18:04 ` James Dutton
2022-10-03 18:17   ` Alan Stern [this message]
2022-10-03 20:21     ` James Dutton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YzsnSPEfBesJRr9R@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=james.dutton@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox