linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Julian Sikorski <belegdol@gmail.com>
Cc: Oliver Neukum <oneukum@suse.com>,
	Nathan Stratton Treadway <vgerlists@nathanst.com>,
	linux-usb@vger.kernel.org, hdegoede@redhat.com
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Tue, 20 Jul 2021 09:43:14 +0200	[thread overview]
Message-ID: <YPZ+kv70G3OuCEp0@kroah.com> (raw)
In-Reply-To: <56cebf15-cf9d-475f-b388-b2be723697f6@gmail.com>

On Mon, Jul 19, 2021 at 06:10:10PM +0200, Julian Sikorski wrote:
> W dniu 19.07.2021 o 14:47, Oliver Neukum pisze:
> > 
> > > Hi all,
> > > 
> > > apologies for necro-ing this thread. I have just tried this drive with
> > > my new laptop (Asus ZenBook UM425IA) and the same quirk was needed to
> > > get the drive to work:
> > > options usb-storage quirks=059f:1061:u
> > > 
> > > Should we still try to get uas working with this drive or should I
> > > send a patch hardcoding a quirk? I am on 5.13.2-300.fc34.x86_64 kernel
> > > now. Thanks for the feedback in advance.
> > > 
> > 
> > Hi,
> > 
> > 
> > sometimes we must give up. This thing is too elusive. Please send a
> > patch with a quirk.
> > 
> >      Regards
> > 
> >          Oliver
> > 
> > 
> 
> Hi,
> 
> thanks for confirming. Patch is attached, it appears to be working correctly
> when applied against 5.13.3. Please let me know if changes are required.
> 
> Best regards,
> Julian

> >From 01057f40aaf0036271dc401add9310dc63bfbcc1 Mon Sep 17 00:00:00 2001
> From: Julian Sikorski <belegdol+github@gmail.com>
> Date: Mon, 19 Jul 2021 17:27:16 +0200
> Subject: [PATCH] Add LaCie Rugged USB3-FW to IGNORE_UAS
> 
> LaCie Rugged USB3-FW appears to be incompatible with UAS. It generates
> errors like:
> [ 1151.582598] sd 14:0:0:0: tag#16 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
> [ 1151.582602] sd 14:0:0:0: tag#16 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
> [ 1151.588594] scsi host14: uas_eh_device_reset_handler start
> [ 1151.710482] usb 2-4: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
> [ 1151.741398] scsi host14: uas_eh_device_reset_handler success
> [ 1181.785534] scsi host14: uas_eh_device_reset_handler start
> ---
>  drivers/usb/storage/unusual_uas.h | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
> index f9677a5ec31b..c35a6db993f1 100644
> --- a/drivers/usb/storage/unusual_uas.h
> +++ b/drivers/usb/storage/unusual_uas.h
> @@ -45,6 +45,13 @@ UNUSUAL_DEV(0x059f, 0x105f, 0x0000, 0x9999,
>  		USB_SC_DEVICE, USB_PR_DEVICE, NULL,
>  		US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME),
>  
> +/* Reported-by: Julian Sikorski <belegdol@gmail.com> */
> +UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999,
> +		"LaCie",
> +		"Rugged USB3-FW",
> +		USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> +		US_FL_IGNORE_UAS),
> +
>  /*
>   * Apricorn USB3 dongle sometimes returns "USBSUSBSUSBS" in response to SCSI
>   * commands in UAS mode.  Observed with the 1.28 firmware; are there others?
> -- 
> 2.31.1
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch was attached, please place it inline so that it can be
  applied directly from the email message itself.

- Your patch does not have a Signed-off-by: line.  Please read the
  kernel file, Documentation/SubmittingPatches and resend it after
  adding that line.  Note, the line needs to be in the body of the
  email, before the patch, not at the bottom of the patch or in the
  email signature.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

  reply	other threads:[~2021-07-20  9: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
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 [this message]
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=YPZ+kv70G3OuCEp0@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=belegdol@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --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).