<div dir="ltr"><div><div><div>Hi!<br><br></div>Some more info.<br></div>I've tried to compile kernel using config from Linux Mint. Compilation of the kernel source that comes with distro failed because of some missing files. However, I was able to compile kernel 3.18 using config from Mint. Sadly, the problem was still there.<br><br></div>After that I've tried to inspect versions of brasero and libs used in different distros. It seems that Mint uses brasero 3.10.0 and Debian Uses brasero 3.11.4. I've decided not to revert back just now (something else may break). However, Mint uses libburn4 version 1.3.4 instead of 1.3.2 in Debian. So I've downloaded and compiled 1.3.4 versions of libburn, libisoburn and libisofs. After that I've tried brasero again and it failed, but with different error. Seems to me that libburn/libisoburn is the main cause of problems. <br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-23 19:01 GMT+03:00 Дмитрий Нестеркин <span dir="ltr"><<a href="mailto:undelborg@gmail.com" target="_blank">undelborg@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hello.<br></div><div><br>Well, bad news.<br></div>No kernel version I've tested worked. I've tried: 3.18.16, 3.19.8, 4.0.6. All kernels were compiled with .config file currently present in my system (default one that comes with distro).<br></div>All kernel tests ended with "[5 21 02] Illegal request. Invalid address for write"<br></div>Debian Live DVD does not work either.<br><br></div>Kernel modules you requested:<br>dmitry@D-NESTERKIN:~$ sudo lsmod |grep usb<br>[sudo] password for dmitry: <br>usbhid 44460 0 <br>btusb 29721 0 <br>bluetooth 374429 1 btusb<br>hid 102264 2 hid_generic,usbhid<br>usb_storage 56215 0 <br>scsi_mod 191405 5 sg,usb_storage,libata,sd_mod,sr_mod<br>usbcore 195340 7 btusb,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid,xhci_hcd<br>usb_common 12440 1 usbcore<br>dmitry@D-NESTERKIN:~$<br><br>dmitry@D-NESTERKIN:~$ sudo lsmod |grep scsi<br>scsi_mod 191405 5 sg,usb_storage,libata,sd_mod,sr_mod<br>dmitry@D-NESTERKIN:~$ <br><br>dmitry@D-NESTERKIN:~$ sudo lsmod |grep ata<br>libata 177457 2 ahci,libahci<br>scsi_mod 191405 5 sg,usb_storage,libata,sd_mod,sr_mod<br>dmitry@D-NESTERKIN:~$ <br><br></div>I've also tried to install firmware-linux-free and firmware-linux-nonfree packages with no luck.<br><div><br></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">2015-06-23 10:23 GMT+03:00 Дмитрий Нестеркин <span dir="ltr"><<a href="mailto:undelborg@gmail.com" target="_blank">undelborg@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">One more: when I first booted with new kernel, some resets were logged:<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.468462] usb 1-3.3: new high-speed USB device number 4 using xhci_hcd<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559042] usb 1-3.3: New USB device found, idVendor=093b, idProduct=0023<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559047] usb 1-3.3: New USB device strings: Mfr=85, Product=57, SerialNumber=44<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559050] usb 1-3.3: Product: PLEXTOR USB Storage Adapter<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559053] usb 1-3.3: Manufacturer: PLEXTOR<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 2.559055] usb 1-3.3: SerialNumber: ABC10CA1F554<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 5.422571] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 6.491309] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 7.559969] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd<br>Jun 23 10:09:34 D-NESTERKIN kernel: [ 8.628865] usb 1-3.3: reset high-speed USB device number 4 using xhci_hcd<br><br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-23 10:21 GMT+03:00 Дмитрий Нестеркин <span dir="ltr"><<a href="mailto:undelborg@gmail.com" target="_blank">undelborg@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Kernel 3.18.16 gives me exactly the same error.<br></div>At the moment, I need to do some work stuff, but I'll be doing more experiments ASAP.<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-23 0:42 GMT+03:00 Дмитрий Нестеркин <span dir="ltr"><<a href="mailto:undelborg@gmail.com" target="_blank">undelborg@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>I've downloaded 3.18.16 longterm kernel and plan to compile it on my system.<br></div>Linux Mint (which is OK) uses kernel 3.13 and fedora 22 uses kernel 4.0 (also ok).<br></div>In fact there is a lot of UAS/USB bugs reported for kernel 3.16 (and some for 3.15 and 3.17).<br><br></div>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.<br></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">2015-06-22 21:34 GMT+03:00 Thomas Schmitt <span dir="ltr"><<a href="mailto:scdbackup@gmx.net" target="_blank">scdbackup@gmx.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span><br>
> I have found some interesting discussion about UAS bugs in kernel 3.16:<br>
> <a href="https://lists.debian.org/debian-kernel/2014/07/msg00318.html" rel="noreferrer" target="_blank">https://lists.debian.org/debian-kernel/2014/07/msg00318.html</a><br>
<br>
</span>UAS ... google ... wikipedia ...<br>
Well, it would be the natural way to perform SG_IO with a USB<br>
device. Burn programs issue SCSI commands and UAS is designed<br>
for transporting them. Wikipedia has:<br>
"Version 3.18-rc4 of the Linux kernel disables buggy UAS<br>
implementation in xHCI host controllers Etron EJ168,<br>
ASMedia ASM1042,[19] and VIA VL80x.[20]"<br>
<br>
But i understand that UAS is quite a new protocol.<br>
Is your drive's USB controller young enough ? (Actually<br>
i assume the drive is SATA or IDE and the box has a<br>
USB-SATA or USB-IDE bridge bridge.)<br>
<span><br>
<br>
> An here comes the output from my kern.log:<br>
</span><span>> Jun 22 15:12:02 D-NESTERKIN kernel: [ 1.508233] usb 3-2: Product: PLEXTOR<br>
> USB Storage Adapter<br>
<br>
</span>They really give few clue about age and version of the<br>
drive-side USB controller.<br>
I googled for "PLEXTOR USB Storage Adapter" "UAS" and found<br>
nearly nothing. Descriptions of UAS refer to hard disks and<br>
SSDs, rather than optical drives. But - as stated - i expect<br>
it to depend on the USB-SATA or USB-IDE controller of the<br>
drive box.<br>
<br>
<br>
In any case, recent changes in USB are obvious suspects.<br>
Now i'm curious whether the working and non-working Linuxes<br>
show a pattern with kernel revisions.<br>
<div><div><br>
<br>
Have a nice day :)<br>
<br>
Thomas<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span>-- <br><div>С уважением,<br>Нестеркин Дмитрий</div>
</span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div>С уважением,<br>Нестеркин Дмитрий</div>
</div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div>С уважением,<br>Нестеркин Дмитрий</div>
</div>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="">-- <br><div>Best regards,<br>Dmitry Nesterkin<br></div>
</span></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">С уважением,<br>Нестеркин Дмитрий</div>
</div>