From: Brice Goglin <brice.goglin@gmail.com>
To: Cyril Roelandt <tipecaml@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
sellis@redhat.com, pachoramos@gmail.com,
labbott@fedoraproject.org, gregkh@linuxfoundation.org,
javhera@gmx.com
Subject: Re: [BUG] Regression in Linux 5.4.17 for JMicron JMS566 enclosure
Date: Mon, 24 Aug 2020 00:14:38 +0200 [thread overview]
Message-ID: <558e1879-e17a-6185-70db-b45c3f640596@gmail.com> (raw)
In-Reply-To: <20200823180837.GA3448@Susan>
Le 23/08/2020 à 20:08, Cyril Roelandt a écrit :
> Hello,
>
> On 2020-08-23 10:47, Alan Stern wrote:
>> Yes; it looks like the problem is that there are entries for this device
>> in both unusual_devs.h and unusual_uas.h -- and it doesn't help that the
>> two entries aren't identical.
>>
>> The unusual_devs.h entry tells usb-storage not to use FUA, but it
>> doesn't rule out the uas driver. And since the device claims to support
>> UAS, usb-storage bows out. But then the unusual_uas.h entry tells uas
>> not to handle the drive, so the end result is that it doesn't get
>> handled at all.
>>
>> To fix the immediate problem you should add the US_FL_IGNORE_UAS flag to
>> the entry in unusual_devs.h.
> That did the trick[1]. Do you think this patch could be suitable for a
> future version of the kernel?
It fixes my issue too (on top of 5.7.17).
Brice
next prev parent reply other threads:[~2020-08-23 22:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 20:56 [BUG] Regression in Linux 5.4.17 for JMicron JMS566 enclosure Cyril Roelandt
2020-04-16 1:21 ` Alan Stern
[not found] ` <CABLbxQ2Hoq8zt--w2FwuMa6FRCC72E5a-tvGRQOm=C0YF7bfqA@mail.gmail.com>
2020-04-16 14:43 ` Pacho Ramos
2020-04-17 18:32 ` Cyril Roelandt
2020-04-17 20:06 ` Alan Stern
2020-04-17 22:09 ` Cyril Roelandt
2020-04-19 16:03 ` Alan Stern
2020-04-21 3:01 ` Cyril Roelandt
2020-04-21 13:58 ` Alan Stern
2020-08-15 0:18 ` Cyril Roelandt
2020-08-15 2:19 ` Alan Stern
2020-08-15 23:23 ` Cyril Roelandt
2020-08-16 16:26 ` Alan Stern
2020-08-18 4:13 ` Cyril Roelandt
2020-08-18 14:57 ` Alan Stern
2020-08-23 1:30 ` Cyril Roelandt
2020-08-23 14:47 ` Alan Stern
2020-08-23 18:08 ` Cyril Roelandt
2020-08-23 22:14 ` Brice Goglin [this message]
2020-08-24 7:40 ` Greg KH
2020-08-24 17:31 ` [PATCH] Ignore UAS for JMicron JMS567 ATA/ATAPI Bridge Cyril Roelandt
2020-08-24 20:18 ` Alan Stern
2020-08-25 21:22 ` [PATCH v2] " Cyril Roelandt
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=558e1879-e17a-6185-70db-b45c3f640596@gmail.com \
--to=brice.goglin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=javhera@gmx.com \
--cc=labbott@fedoraproject.org \
--cc=linux-usb@vger.kernel.org \
--cc=pachoramos@gmail.com \
--cc=sellis@redhat.com \
--cc=stern@rowland.harvard.edu \
--cc=tipecaml@gmail.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).