From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216282] New: usb-mass storage
Date: Mon, 25 Jul 2022 22:39:01 +0000 [thread overview]
Message-ID: <bug-216282-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216282
Bug ID: 216282
Summary: usb-mass storage
Product: Drivers
Version: 2.5
Kernel Version: 5.15.0-41-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: audioprof2001@yahoo.com
Regression: No
since Groovy Gorilla, maybe older...
problem #1.
usb mass storage,
delay time is too fast, and there is No .conf in /modprobe.d
i have to unplug and plug again the external usb hdd cable turned-on
so Linux can detect the HDD and mount.
ASM1051 is detected with $ lsusb
when i turn-on,
but the HDD is Not Detected, because delay time is too fast/short.
its like turning-on without a HDD.
upgraded the firmware of the external USB IC controller to latest.
https://github.com/juanpc2018/Asmedia-AS2105-sata-to-USB-3
because large HDDs "over 2TB" was Not working,
Now works ok exept that problem in Linux.
Windows8.1x64 works OK.
problem #2.
Linux detects a different speed?.
$ lsusb
Bus 002 Device 004: ID 174c:5106 ASMedia Technology Inc. ASM1051 SATA 3Gb/s
bridge
is Not 3Gb/s = 375MB/s.
is 5Gb/s = 550MB/s
when used with SSD,
large 18TB HDD are 250MB/s.
there is something strange going on with usb-mass-storage.
https://support.apple.com/kb/SP710?locale=en_US
--
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 reply other threads:[~2022-07-25 22:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 22:39 bugzilla-daemon [this message]
2022-07-26 1:20 ` [Bug 216282] usb-mass storage 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
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@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).