From: Jonathan Woithe <jwoithe@just42.net>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-usb@vger.kernel.org, Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: Samsung T5 500 GB USB3.1 SSD fails with ASMedia ASM1142, 250 GB version works
Date: Fri, 26 Feb 2021 23:02:33 +1030 [thread overview]
Message-ID: <20210226123232.GA26589@marvin.atrad.com.au> (raw)
In-Reply-To: <20210222111707.GA26487@marvin.atrad.com.au>
On Mon, Feb 22, 2021 at 09:47:07PM +1030, Jonathan Woithe wrote:
> On Mon, Feb 22, 2021 at 11:24:18AM +0100, Oliver Neukum wrote:
> > It is possible that the other machine can just supply more power.
>
> On the machine with the ASMedia controller (where the problem occurs), the
> 500 GB SSD works perfectly well when connected to USB2 sockets. If a USB2
> socket can supply sufficient power, wouldn't a USB3 port be more than
> capable?
>
> The specifications for both the 250 GB (working) and 500 GB (not working)
> are 5V at 0.8A. I'm guessing this is a worst-case scenario. In any case,
> this is well within the capabilities of a USB3 port. If there was a power
> issue with one of these drives it's surprising it's not seen in both -
> unless the 250 GB is just under the critical power threshold and the 500 GB
> is just above it. Is there an easy way to tell if this is indeed the case?
Another datapoint: on the system with the ASMedia controller where the 250
GB T5 SSD works but the 500 GB T5 SSD does not, the same USB3 socket is able
to power a traditional 2.5" spinning rust hard drive without any obvious
problems.
Regards
jonathan
prev parent reply other threads:[~2021-02-26 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 10:22 Samsung T5 500 GB USB3.1 SSD fails with ASMedia ASM1142, 250 GB version works Jonathan Woithe
2021-02-22 10:24 ` Oliver Neukum
2021-02-22 11:17 ` Jonathan Woithe
2021-02-26 12:32 ` Jonathan Woithe [this message]
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=20210226123232.GA26589@marvin.atrad.com.au \
--to=jwoithe@just42.net \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=oneukum@suse.com \
/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