linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216282] usb-mass storage
Date: Fri, 29 Jul 2022 20:06:34 +0000	[thread overview]
Message-ID: <bug-216282-208809-icsnlM87c5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216282-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216282

--- Comment #21 from Alan Stern (stern@rowland.harvard.edu) ---
It looks like you may be right about the initial time delay being too small.  I
don't see any significant differences in the usbmon trace between the initial
plug-in and the later one, except that the device failed to respond during the
initial plug-in when asked to identify itself.

(You can compare them yourself just by looking at the trace file.  The initial
plug-in is detected at line 7, and the second plug-in is detected at line 193. 
The lines subsequent to those are virtually identical if you ignore the first
two columns, with just one or two unimportant differences -- up until the
failure at line 75.)

You can change the length of the time delay by setting the usb-storage
delay_use parameter.  For instance, assuming that the usb-storage module is
already loaded, do:

   echo 20 >/sys/module/usb_storage/parameters/delay_use

before you plug in the drive.  That will change the delay to 20 seconds (the
default delay value is 1 second).  Maybe it will help.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-07-29 20:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 22:39 [Bug 216282] New: usb-mass storage bugzilla-daemon
2022-07-26  1:20 ` [Bug 216282] " bugzilla-daemon
2022-07-26  2:49 ` bugzilla-daemon
2022-07-26  3:07 ` bugzilla-daemon
2022-07-26  3:13 ` bugzilla-daemon
2022-07-26  3:41 ` bugzilla-daemon
2022-07-26  4:04 ` bugzilla-daemon
2022-07-26  4:25 ` bugzilla-daemon
2022-07-26 14:15 ` bugzilla-daemon
2022-07-26 15:45 ` bugzilla-daemon
2022-07-26 17:38 ` bugzilla-daemon
2022-07-26 19:20 ` bugzilla-daemon
2022-07-27  1:21 ` bugzilla-daemon
2022-07-27  1:42 ` bugzilla-daemon
2022-07-27  1:43 ` bugzilla-daemon
2022-07-27  1:45 ` bugzilla-daemon
2022-07-27 14:01 ` bugzilla-daemon
2022-07-28  3:44 ` bugzilla-daemon
2022-07-28  3:50 ` bugzilla-daemon
2022-07-28 14:42 ` bugzilla-daemon
2022-07-29 18:39 ` bugzilla-daemon
2022-07-29 20:06 ` bugzilla-daemon [this message]
2022-07-29 22:35 ` bugzilla-daemon
2022-07-30  2:38 ` bugzilla-daemon
2022-07-30  2:45 ` bugzilla-daemon

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=bug-216282-208809-icsnlM87c5@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).