> Solved: > > By installing a the latest kernel and headers from Debian backports solved the > problem: > > apt-get -t jessie-backports install linux-image-amd64 linux-headers-amd64 > > Info about backports configuration: > http://backports.debian.org/Instructions/ > > # uname -a > Linux panther 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 (2015-12-14) > x86_64 GNU/Linux > > After this nigtmare-ish experience I would suggest the debian maintainers > to trash the default jessie kernel 3.16 and replace it with the above > 4.2 kernel; otherwise unexperienced users will wonder why their new SSD etc. > isn't working in debian/ubuntu & co., as happened to me... :-( I have missed that your message. Solved? Amazing, because the patch I had in mind was not applied to 4.2.6. Also the device you are reporting has different productId. I think that in newer kernels (4.x) another driver is used (UAS), which has already given device logged as "special", see https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/storage/unusual_uas.h#n145 /* Reported-by: Takeo Nakayama <javhera@xxxxxxx> */ UNUSUAL_DEV(0x357d, 0x7788, 0x0000, 0x9999, "JMicron", "JMS566", USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_NO_REPORT_OPCODES), However it does not have US_FL_BROKEN_FUA flag set. Mystery. -- With best regards, Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
