Yes, I could confirm this by adding some debug printing to the ums-cypress module:
Running scsi_id does nothing (no results, no errors, no atacb commands).
Running stock ata_id:
creates atacb command 0xEC (ATA IDENTIFY DEVICE)
hangs, usb reset after 30s
HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument
Running my own (patched, no v3 SG_IO) ata_id:
HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument
(but no atacb commands translated by ums-cypress)
Running hdparm:
creates atacb with command 0xEC (ATA IDENTIFY DEVICE)
hangs, usb reset after 16s
creates atacb with command 0xA1 (ATA IDENTIFY PACKET DEVICE)
hangs, usb reset after 16s
In all cases of atacb commands above, the srb->result returned from usb_stor_transparent_scsi_command() in cypress_atacb.c is 50000.
Yes, I could confirm this by adding some debug printing to the ums-cypress module:
Running scsi_id does nothing (no results, no errors, no atacb commands).
Running stock ata_id:
creates atacb command 0xEC (ATA IDENTIFY DEVICE)
hangs, usb reset after 30s
HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument
Running my own (patched, no v3 SG_IO) ata_id:
HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument
(but no atacb commands translated by ums-cypress)
Running hdparm:
creates atacb with command 0xEC (ATA IDENTIFY DEVICE)
hangs, usb reset after 16s
creates atacb with command 0xA1 (ATA IDENTIFY PACKET DEVICE)
hangs, usb reset after 16s
In all cases of atacb commands above, the srb->result returned from usb_stor_ transparent_ scsi_command( ) in cypress_atacb.c is 50000.