On Tue, 10 Nov 2015, Dmitry Katsubo wrote: > Hello everyone, > > Sorry for cross-posting from linux-scsi@xxxxxxxxxxxxxxx > > In continuation to the issue described in [1] and [2]: > > Unfortunately, I still suffer from the same problem on Linux kernel > v4.2.3. The problem is in detailed described in [3], in particular I see > the following in dmesg: > > sd 6:0:0:0: [sdd] 234441648 512-byte logical blocks: (120 GB/111 GiB) > sd 6:0:0:0: [sdd] 4096-byte physical blocks > sd 6:0:0:0: [sdd] Write Protect is off > sd 6:0:0:0: [sdd] Mode Sense: 53 00 10 08 > sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, supports > DPO and FUA > ... > sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE > sd 6:0:0:0: [sdd] tag#0 Sense Key : Illegal Request [current] > sd 6:0:0:0: [sdd] tag#0 Add. Sense: Invalid field in cdb > sd 6:0:0:0: [sdd] tag#0 CDB: Write(10) 2a 08 00 00 10 80 00 00 08 00 > blk_update_request: critical target error, dev sdd, sector 4224 > BTRFS: lost page write due to I/O error on /dev/sdd1 > BTRFS: bdev /dev/sdd1 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 > > I believe that according to patches [4], [5] I should see something like > "Disabling FUA" in logs, but that is not the case > > Any information about how to fix the problem is appreciated. > > # lsusb > Bus 001 Device 007: ID 152d:0567 JMicron Technology Corp. / JMicron USA > Technology Corp. Please post the output from lsusb -v. Probably your device has a bcdDevice value that's outside the range in the blacklist entry. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
