weird, not, it is little bit more stable, bu then it eventually hit
the problem again:
[ 2696.410684] sd 2:0:0:2: [sdc] tag#13 uas_eh_abort_handler 0 uas-tag
14 inflight: CMD OUT
[ 2696.410708] sd 2:0:0:2: [sdc] tag#13 CDB: Write(10) 2a 00 19 ed 69
80 00 00 20 00
[ 2696.410948] sd 2:0:0:2: [sdc] t
Upgraded to 4.15.3 and now UAS works, strange...
Anyhow now the enclosure is connected via an USB 3.0 HUB (self powered
in my case) and it seems to be stable
Devs, apparently there is some problem operating this chipset with
Intel USB controller directly
I have googled a little bit aroud and actual
That is very strange
My device has same vid:pid of your one, but it goes blacklisted...
I am running kernel 4.15.1, I will try to upgrade
What kind of enclosure is yours? Mine is an Orico 9553RU3 5 bay
enclosure with RAID
Bye
2018-02-13 23:41 GMT+01:00 Chris Murphy :
> On Mon, Feb 12, 2018 at 12:5
On Mon, Feb 12, 2018 at 12:57 AM, Menion wrote:
>
> I wanted to test my enclosure with an hub, but I have just realized
> that now the JMS567 is UAS blacklisted by default in kernel
> 4.15.x.
> Can you check if it still works removing the dedicated hub external
> power supply?
I've upgr
2018-02-10 1:00 GMT+01:00 Chris Murphy :
> On Fri, Feb 9, 2018 at 3:57 AM, Menion wrote:
>> There are multiple reports of UAS issue together with JMS567 (from myself
>> also)
>> Question: you mentioned that connecting the enclosure to an
>> intermediate USB HUB is a workaround.
>> Can you specify
On Fri, Feb 9, 2018 at 3:57 AM, Menion wrote:
> There are multiple reports of UAS issue together with JMS567 (from myself
> also)
> Question: you mentioned that connecting the enclosure to an
> intermediate USB HUB is a workaround.
> Can you specify if your PC USB port is USB 3.0 and if the HUB i
There are multiple reports of UAS issue together with JMS567 (from myself also)
Question: you mentioned that connecting the enclosure to an
intermediate USB HUB is a workaround.
Can you specify if your PC USB port is USB 3.0 and if the HUB is USB
3.0 as well, and if it is self-powered or not?
2018
Problem summary:
Out of the box, a USB 3.0 SATA 6.0 enclosure, hangs during reads or
writes and spits out some errors, when directly connected to a
computer's USB port. When connected via a USB hub, uas is still used,
but the errors do not occur. When setting a quirk to blacklist the
drive from uas
