From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216282] usb-mass storage
Date: Tue, 26 Jul 2022 01:20:08 +0000 [thread overview]
Message-ID: <bug-216282-208809-pJTxoh36kX@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 #1 from Alan Stern (stern@rowland.harvard.edu) ---
What delay time are you referring to?
What speed does Linux detect?
What does "lsusb -v" show for this drive?
What shows up in the dmesg log when the HDD is detected and when it is not
detected?
In your lsusb output, where it says "ASM1051 SATA 3Gb/s bridge", that 3Gb/s
speed is not what Linux detects; it is part of the device's product name.
--
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 1:20 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 ` bugzilla-daemon [this message]
2022-07-26 2:49 ` [Bug 216282] " 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
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-pJTxoh36kX@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).