All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tj (Elloe Linux)" <ml.linux@elloe.vision>
To: Oliver Neukum <oneukum@suse.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	linux-usb <linux-usb@vger.kernel.org>
Subject: Re: uas: bug: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 6 inflight: IN
Date: Mon, 20 Jul 2020 18:18:47 +0100	[thread overview]
Message-ID: <d22abd9c-0b04-f4a2-0f38-e271b5de2aa6@elloe.vision> (raw)
In-Reply-To: <1595235102.2531.7.camel@suse.de>

On 20/07/2020 09:51, Oliver Neukum wrote:
> Am Sonntag, den 19.07.2020, 12:55 +0100 schrieb Tj (Elloe Linux):
>> On 19/07/2020 12:09, Greg KH wrote:
>>> On Sun, Jul 19, 2020 at 11:22:10AM +0100, Tj (Elloe Linux) wrote:
> 
>>> Where is an error here?  Those looks ok to me.
>>
>> These repeated 'zaps' and resets every 30 seconds or so are not errors?
> 
> They are errors. But whose errors? 0x28 looks like a READ10 to me.

Update for today: setting a quirk to not use UAS allows the device to
work without any apparent failures.

usb-storage.quirks=0x152d:0x0562:u

I plan on capturing a USB debug log with and without the
quirk tomorrow.

  parent reply	other threads:[~2020-07-20 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 10:22 uas: bug: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 6 inflight: IN Tj (Elloe Linux)
2020-07-19 11:09 ` Greg KH
2020-07-19 11:55   ` Tj (Elloe Linux)
2020-07-20  8:51     ` Oliver Neukum
2020-07-20 10:25       ` Tj (Elloe Linux)
2020-07-26  8:59         ` uas: bug: [turris-L1 #1096031] MOX Hardware Issue - USB SuperSpeed ports resetting constantly Tj (Elloe Linux)
2020-07-20 17:18       ` Tj (Elloe Linux) [this message]
2020-07-19 14:31 ` uas: bug: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 6 inflight: IN Alan Stern
2020-07-19 15:01   ` Tj (Elloe Linux)

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=d22abd9c-0b04-f4a2-0f38-e271b5de2aa6@elloe.vision \
    --to=ml.linux@elloe.vision \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.