linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David C. Partridge" <david.partridge@perdrix.co.uk>
To: "'Alan Stern'" <stern@rowland.harvard.edu>
Cc: "'Oliver Neukum'" <oneukum@suse.com>, <linux-usb@vger.kernel.org>
Subject: RE: Issues with LaCie USB3 drive and UAS
Date: Tue, 8 Dec 2020 20:00:52 -0000	[thread overview]
Message-ID: <003e01d6cd9c$d8777cf0$896676d0$@perdrix.co.uk> (raw)
In-Reply-To: <20201208174515.GG1298255@rowland.harvard.edu>

Thank you to both Oliver and to you.

I'll chase up the supplier over the cable.

Would I be right to assume that this LaCie device (and other Seagate USB
devices) will the added to the database of quirks? So that when Oliver's fix
goes "mainstream" no-one will need to add options for modprobe?

Hmm I wonder how long it will take the Ubuntu Kernel to catch up with
Olivers patch?

Thanks again,
David

-----Original Message-----
From: 'Alan Stern' <stern@rowland.harvard.edu> 
Sent: 08 December 2020 17:45
To: David C. Partridge <david.partridge@perdrix.co.uk>
Cc: 'Oliver Neukum' <oneukum@suse.com>; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

On Tue, Dec 08, 2020 at 04:47:44PM -0000, David C. Partridge wrote:
> >This is puzzling.  The device connected at SuperSpeed in the previous
> tests.  Clearly this is related to the warning in the preceding line (the
> port failed to configure its link partner).
> 
> >What could have happened?  A problem in the cable?
> 
> Previous test was using a 3m long cable.
> 
> Tried again with a 1m cable:
> 
> Dec 08 16:38:30 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device
> number 2 using xhci_hcd
...

So it worked.

> I then tried again using the 3m long cable and got the same error as
before
> and connected at high-speed not SuperSpeed
> 
> Should I expect problems with a 3m long cable or does this say the 3m long
> cable is faulty? 

IT depends on the thickness (gauge) of the wires inside the cable.  
There's a table (11-3) in the USB-3.1 spec that lists maximum cable 
length for a variety of gauges.

For AWG 28 the maximum cable length is 0.8 meters.  For AWG 20 the 
maximum length is 5.3 meters.  Your cable is likely to be somewhere in 
that range, but I don't know where.

On the bright side, it looks like you have found the answer to all the 
problems.  :-)

Alan Stern


  reply	other threads:[~2020-12-08 20:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-08 10:56 Issues with LaCie USB3 drive and UAS David C. Partridge
2020-11-09  9:29 ` Oliver Neukum
2020-11-09  9:51   ` David C. Partridge
2020-11-09 10:13     ` Oliver Neukum
2020-11-09 11:21       ` David C. Partridge
2020-11-09 15:21         ` David C. Partridge
2020-11-09 16:47           ` David C. Partridge
2020-11-11 11:43           ` Oliver Neukum
2020-11-11 15:50             ` David C. Partridge
2020-11-11 19:18               ` Oliver Neukum
2020-11-11 20:54                 ` David C. Partridge
2020-11-23 14:59                   ` Oliver Neukum
2020-11-25 12:25             ` David C. Partridge
2020-11-26  8:24               ` Oliver Neukum
2020-11-26  9:33                 ` David C. Partridge
2020-11-26 10:22                   ` Oliver Neukum
     [not found]                     ` <0000 01d6c89c$086812e0$193838a0$@perdrix.co.uk>
2020-12-02 11:12                     ` David C. Partridge
     [not found]                       ` <612be9a9cd6ffdb9492781e174859c7b4e69 4a86.camel@suse.com>
2020-12-02 11:38                       ` Oliver Neukum
2020-12-02 13:39                         ` David C. Partridge
2020-12-03  2:11                         ` David C. Partridge
2020-12-03 13:16                           ` Oliver Neukum
2020-12-03 14:30                             ` David C. Partridge
2020-12-07 10:53                               ` David C. Partridge
2020-12-08 14:03                                 ` Oliver Neukum
2020-12-08 16:06                                   ` David C. Partridge
2020-12-08 16:27                                     ` Alan Stern
2020-12-08 16:47                                       ` David C. Partridge
2020-12-08 17:45                                         ` 'Alan Stern'
2020-12-08 20:00                                           ` David C. Partridge [this message]
2020-12-09 11:11                                             ` Oliver Neukum
2020-12-03 14:06                           ` Oliver Neukum
2020-12-03 14:46                             ` David C. Partridge
2020-12-03 16:16                               ` Alan Stern

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='003e01d6cd9c$d8777cf0$896676d0$@perdrix.co.uk' \
    --to=david.partridge@perdrix.co.uk \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    /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).