2018-02-06 11:18 GMT+01:00 Oliver Neukum :
> Am Mittwoch, den 31.01.2018, 12:45 +0100 schrieb Menion:
>> you can see that short while after the two HD are mounted I start to
>> get any sort of USB command errors.
>
> Well, no, all errors are Write(10). Thus my question whether you can
> trigger it
Am Mittwoch, den 31.01.2018, 12:45 +0100 schrieb Menion:
> you can see that short while after the two HD are mounted I start to
> get any sort of USB command errors.
Well, no, all errors are Write(10). Thus my question whether you can
trigger it with any other command. Does it error out with Read(
Hello
Actually the mentioned ones are the very first synthomps that
something is going wrong:
Jan 27 08:56:06 Menionubuntu systemd[1]:
dev-disk-by\x2duuid-ba1e0d88\x2d2e26\x2d499d\x2d8fe3\x2d458b9c53349a.device:
Dev dev-disk-by\x2duuid-ba1e0d88\x2d2e26\x2d499d\x2d8fe3\x2d458b9c53349a.device
appear
Am Montag, den 29.01.2018, 14:48 +0100 schrieb Menion:
> As soon as more than one HD in inserted in the enclosure, when
> parallel write operation are send to the HDs, you start to get
> immediately CMD error on UAS driver, after a while the USB gets in an
> inconsistent status and you are forced t
Hello
I am trying to follow up on the original thread, opened on this issue
by Christoph Gohle May 2017 (same email subject)
I confirm that the same issue is still present on kernel 4.14.15
(Mainline build for Ubuntu xenial, amd64)
My enclosure is an Orico 9558RU3, using JMS567 USB 3.0 to SATA brid
> On 24 May 2017, at 21:40, Christoph Gohle wrote:
>
>>
>>> On 22 May 2017, at 14:37, Mathias Nyman
>>> wrote:
>>>
>>> On 22.05.2017 11:48, Christoph Gohle wrote:
Hey Mathias,
> On 19 May 2017, at 09:58, Mathias Nyman
> wrote:
>
>>
>
> 4.11 kerne
Hi Christoph,
Out of curiosity, what exact device is this? I have an multi-disk JMS567
based enclosure which reports the same IDs from lsusb, doesn't work with
uas at all. According to the datasheet for JMS567 it should support UAS,
but I've received conflicting information from the manufacturer o
>
>> On 22 May 2017, at 14:37, Mathias Nyman
>> wrote:
>>
>> On 22.05.2017 11:48, Christoph Gohle wrote:
>>> Hey Mathias,
>>>
>>>
On 19 May 2017, at 09:58, Mathias Nyman
wrote:
>
4.11 kernel has xhci traces enabled, could you try to reproduce it with
4.
OK. now I am stuck as uas remains blacklisted even after removing the entry in
modprobe.d. Why? syslog says:
May 24 09:17:49 gserv kernel: [2.288977] usb 2-2: UAS is blacklisted for
this device, using usb-storage instead
Like this I can’t test.
Cheers,
Christoph
> On 22 May 2017, at 14:37
On 22.05.2017 11:48, Christoph Gohle wrote:
Hey Mathias,
On 19 May 2017, at 09:58, Mathias Nyman wrote:
4.11 kernel has xhci traces enabled, could you try to reproduce it with 4.11?
xhci traces can be enabled with:
echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
If you know h
Hey Mathias,
> On 19 May 2017, at 09:58, Mathias Nyman wrote:
>
>>
>
> 4.11 kernel has xhci traces enabled, could you try to reproduce it with 4.11?
> xhci traces can be enabled with:
>
> echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
>
> If you know how to reliably reproduce thi
On 18.05.2017 17:30, Christoph Gohle wrote:
Hi,
I have seen several reports around the internet regarding failing io on
USB-SATA bridges. However, these reports seem to be partially old and/or fixes
proposed are implemented in my kernel but don’t fix things. Therefore I thought
I report here
On Thu, May 18, 2017 at 04:30:02PM +0200, Christoph Gohle wrote:
> Hi,
>
> I have seen several reports around the internet regarding failing io
> on USB-SATA bridges. However, these reports seem to be partially old
> and/or fixes proposed are implemented in my kernel but don’t fix
> things. Theref
Hi,
I have seen several reports around the internet regarding failing io on
USB-SATA bridges. However, these reports seem to be partially old and/or fixes
proposed are implemented in my kernel but don’t fix things. Therefore I thought
I report here again. If this is know/duplicate please apolog
14 matches
Mail list logo
