On 12/19/10 18:04, Sergey Vlasov wrote:
Could you also get an usbmon trace when you first issue "smartctl -d
sat" on an otherwise idle device, and then do some writes to it?
Maybe the device returns a wrong residue even in this case, but then
subsequent commands issued by smartctl reset the bad state.
I did "smartctl -d sat -a" on the unmounted drive, then mounted it and
wrote some data on it: http://richard.qasl.de/3.mon.out
One possible option is to ignore the bad residue by using the
US_FL_IGNORE_RESIDUE flag for the device - the 0x152d, 0x2329 JMicron
bridge is already in drivers/usb/storage/unusual_devs.h with quirk
flags US_FL_IGNORE_RESIDUE | US_FL_SANE_SENSE, maybe this device needs
such workarounds too. This can be tested without rebuilding the
kernel by specifying an additional parameter for the usb-storage
module:
quirks=1e68:001b:ar
("echo 1e68:001b:ar> /sys/module/usb_storage/parameters/quirks"
should work even without reloading the module).
This seems to work. I can write data on the drive and query SMART
simultaneously without tons of errors and interruption.
--
Regards,
Richard Schütz
--
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
