linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Julian Sikorski <belegdol@gmail.com>,
	Nathan Stratton Treadway <vgerlists@nathanst.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Mon, 09 Sep 2019 14:45:25 +0200	[thread overview]
Message-ID: <1568033125.365.17.camel@suse.com> (raw)
In-Reply-To: <d11b22f3-3f09-2e3f-dc64-956193f2c5d3@gmail.com>

Am Mittwoch, den 04.09.2019, 19:10 +0200 schrieb Julian Sikorski:
> 
> 
> Moreover, does this matter that the two Read Capacity errors only appear 
> after the device is disconnected?

Hi,

yes it does. However, it didn't in the first log I looked at.
Could you check whether the command the failure happens on
is constant? That is, test a few times and look for differences.

	Regards
		Oliver


  reply	other threads:[~2019-09-09 12:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 13:31 Lacie Rugged USB3-FW does not work with UAS Julian Sikorski
2019-08-23 13:39 ` Oliver Neukum
2019-08-23 13:43   ` Julian Sikorski
2019-08-23 14:21     ` Julian Sikorski
2019-08-23 21:23       ` Oliver Neukum
2019-08-24  7:08         ` Julian Sikorski
2019-08-29 18:33           ` Julian Sikorski
2019-09-02 11:42             ` Oliver Neukum
2019-09-02 20:10               ` Julian Sikorski
2019-09-04 15:58                 ` Nathan Stratton Treadway
2019-09-04 17:10                   ` Julian Sikorski
2019-09-09 12:45                     ` Oliver Neukum [this message]
2019-09-09 16:18                       ` Julian Sikorski
2021-07-17  8:28                         ` Julian Sikorski
2021-07-19 12:47                           ` Oliver Neukum
2021-07-19 16:10                             ` Julian Sikorski
2021-07-20  7:43                               ` Greg KH
2021-07-20  9:35                               ` Oliver Neukum
2021-07-27 21:19                               ` Hans de Goede
     [not found]                                 ` <CA+xVL_QEgzb1tu-tzqYPxJF-G_a8czCp=uyZ1JJ9+5xmCcNp2Q@mail.gmail.com>
     [not found]                                   ` <CA+xVL_QrJ9f8-BwVRq1oG_yo2Cd=yQH9=TCm5g=MUO9MmdvRVA@mail.gmail.com>
2021-07-29  8:43                                     ` Oliver Neukum
2021-07-29  9:08                                     ` Hans de Goede
2021-08-01  7:36                                       ` Julian Sikorski
2021-08-01  8:46                                         ` Hans de Goede
     [not found]                                       ` <a645c513-794f-5171-d383-7b40fbb1ba18@gmail.com>
2021-08-01  7:47                                         ` Julian Sikorski
2021-09-12 20:13                                       ` Julian Sikorski
2021-09-13  7:38                                         ` Hans de Goede
     [not found]                                           ` <1f6c3026-143a-2004-24da-1da56e6305be@suse.com>
2021-09-13 11:50                                             ` Hans de Goede

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=1568033125.365.17.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=belegdol@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=vgerlists@nathanst.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;
as well as URLs for NNTP newsgroup(s).