diego torres wrote: > Hi there, > > This seagate drive ST3500630AS is being recognized as NCQ capable by > hdparm, and has the default queue_depth of 31, so i think it should > work ok. But there are some problems when using smartmontools (for > example in short test mode) as seen in dmesg: > > ata2.00: exception Emask 0x2 SAct 0x9 SErr 0x0 action 0x2 frozen > ata2.00: (spurious completions during NCQ issue=0x0 SAct=0x9 FIS=004040a1:00000004) > ata2.00: cmd 61/08:00:f4:28:4e/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 out > res 40/00:00:f4:28:4e/00:00:00:00:00/40 Emask 0x2 (HSM violation) > ata2.00: cmd 61/08:18:dc:c8:d7/00:00:00:00:00/40 tag 3 cdb 0x0 data 4096 out > res 40/00:00:f4:28:4e/00:00:00:00:00/40 Emask 0x2 (HSM violation) > ata2: soft resetting port > ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata2.00: configured for UDMA/133 > ata2: EH complete > sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) > sd 1:0:0:0: [sdb] Write Protect is off > sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 > sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > All this problems dissapear when setting queue_depth to 1. > > After cheking the seagate website, there is no mention to NCQ in the > spec sheet of this drive, although there are models tagged as using > NCQ interface, for example ST3500620AS How reproducible is the problem? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
