One more: when I first booted with new kernel, some resets were logged: Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.468462] usb 1-3.3: new high-speed USB device number 4 using xhci_hcd Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559042] usb 1-3.3: New USB device found, idVendor=093b, idProduct=0023 Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559047] usb 1-3.3: New USB device strings: Mfr=85, Product=57, SerialNumber=44 Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559050] usb 1-3.3: Product: PLEXTOR USB Storage Adapter Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559053] usb 1-3.3: Manufacturer: PLEXTOR Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559055] usb 1-3.3: SerialNumber: ABC10CA1F554 Jun 23 10:09:34 D-NESTERKIN kernel: [ 5.422571] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd Jun 23 10:09:34 D-NESTERKIN kernel: [ 6.491309] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd Jun 23 10:09:34 D-NESTERKIN kernel: [ 7.559969] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd Jun 23 10:09:34 D-NESTERKIN kernel: [ 8.628865] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd
2015-06-23 10:21 GMT+03:00 Дмитрий Нестеркин <undelb...@gmail.com>: > Kernel 3.18.16 gives me exactly the same error. > At the moment, I need to do some work stuff, but I'll be doing more > experiments ASAP. > > 2015-06-23 0:42 GMT+03:00 Дмитрий Нестеркин <undelb...@gmail.com>: > >> I've downloaded 3.18.16 longterm kernel and plan to compile it on my >> system. >> Linux Mint (which is OK) uses kernel 3.13 and fedora 22 uses kernel 4.0 >> (also ok). >> In fact there is a lot of UAS/USB bugs reported for kernel 3.16 (and some >> for 3.15 and 3.17). >> >> Controllers you mentioned are USB 3.0. My drive is definitely USB 2.0. >> However, if it looks like a duck, swim like a duck and quacks like a >> duck... I'll definitely need to try new kernel. >> >> 2015-06-22 21:34 GMT+03:00 Thomas Schmitt <scdbac...@gmx.net>: >> >>> Hi, >>> >>> > I have found some interesting discussion about UAS bugs in kernel 3.16: >>> > https://lists.debian.org/debian-kernel/2014/07/msg00318.html >>> >>> UAS ... google ... wikipedia ... >>> Well, it would be the natural way to perform SG_IO with a USB >>> device. Burn programs issue SCSI commands and UAS is designed >>> for transporting them. Wikipedia has: >>> "Version 3.18-rc4 of the Linux kernel disables buggy UAS >>> implementation in xHCI host controllers Etron EJ168, >>> ASMedia ASM1042,[19] and VIA VL80x.[20]" >>> >>> But i understand that UAS is quite a new protocol. >>> Is your drive's USB controller young enough ? (Actually >>> i assume the drive is SATA or IDE and the box has a >>> USB-SATA or USB-IDE bridge bridge.) >>> >>> >>> > An here comes the output from my kern.log: >>> > Jun 22 15:12:02 D-NESTERKIN kernel: [ 1.508233] usb 3-2: Product: >>> PLEXTOR >>> > USB Storage Adapter >>> >>> They really give few clue about age and version of the >>> drive-side USB controller. >>> I googled for "PLEXTOR USB Storage Adapter" "UAS" and found >>> nearly nothing. Descriptions of UAS refer to hard disks and >>> SSDs, rather than optical drives. But - as stated - i expect >>> it to depend on the USB-SATA or USB-IDE controller of the >>> drive box. >>> >>> >>> In any case, recent changes in USB are obvious suspects. >>> Now i'm curious whether the working and non-working Linuxes >>> show a pattern with kernel revisions. >>> >>> >>> Have a nice day :) >>> >>> Thomas >>> >>> >> >> >> -- >> С уважением, >> Нестеркин Дмитрий >> > > > > -- > С уважением, > Нестеркин Дмитрий > -- С уважением, Нестеркин Дмитрий