> On 24 May 2017, at 21:40, Christoph Gohle <christoph@xxxxxxxxx> wrote: > >> >>> On 22 May 2017, at 14:37, Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx> wrote: >>> >>> On 22.05.2017 11:48, Christoph Gohle wrote: >>>> Hey Mathias, >>>> >>>> >>>>> On 19 May 2017, at 09:58, Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx> 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 this then please enable tracing just before >>>>> triggering this. It generates a lot of data. >>>>> >>>>> -Mathias >>>> I would be able to do xhci traces with a 4.10 kernel (4.10.0-21-generic #23~16.04.1-Ubuntu SMP). Don’t really want to go to 4.11. . Still interested? >>> >>> xhci got more useful tracing support in 4.11, >>> Sure, you can try if there's something in 4.10 > OK. Now I managed (had to update-initramfs, stupid…) > … I decided to give up on this. It seems like neither usb-storage nor uas is really a reliable driver for this device. Even though usb-storage did not show the above errors in the log, in the end I found that storage access was not reliable. hotplugging or unplugging a disk from the device did not work as expected: all disks were initialized again and recieved new device nodes. smartd got confused for some reason (disks changing their identification?). Now i am using the eSATA interface provided by the device instead. That seems to work OK for a couple of days now and has not expressed any of the above symptoms. Anyway, thanks for your help. Christoph -- Christoph Gohle christoph@xxxxxxxxx
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
