From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216282] usb-mass storage
Date: Tue, 26 Jul 2022 14:15:25 +0000 [thread overview]
Message-ID: <bug-216282-208809-JoSXzSlyJb@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 #8 from Alan Stern (stern@rowland.harvard.edu) ---
Some of the things you wrote above are not correct. "When you Turn-on the
USB3.0 to SATA controller, electrons travel near the speed of light." Not true
at all; electric waves travel near the speed of light but the electrons
themselves move at only a few centimeters per second (bulk motion).
Anyway, the information you reported doesn't indicate what's going wrong. I
don't think it's simply a matter of waiting for the disk to spin up; the
commands sent by the kernel have a 30-second timeout and that should be plenty
of time.
A usbmon trace of a non-working connection should help. Before you plug in the
USB cable, do:
cat /sys/kernel/debug/usb/usbmon/2u >mon.out
Then after the drive has been plugged in and the drive has failed to appear,
kill the "cat" process with ^C and attach the mon.out file to this bug report.
In fact, you might want to do this twice: once where the drive doesn't work,
and once where it does work, for comparison.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-07-26 14:15 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 [this message]
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
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-JoSXzSlyJb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.