Hello, Robert Hancock wrote: > I don't think the driver is to blame for this one. CPB resp_flags of 2 > indicates the controller says that tag is "released", i.e. drive has > been given the command but not completed. If it's timing out in that > state, either the NCQ implementation is bad enough that it allows > certain queued commands to starve for over 30 seconds, or the drive is > just forgetting about them entirely. > > Unfortunately, if the firmware revision does indeed appear the same on > both sets of drives, the only automated way we could likely address the > problem would be to blacklist NCQ on all of those drives of that > model/revision.. Hmm... it's weird that this problem hasn't been reported on other controllers. Lanstein, can you be persuaded into trying out another NCQ capable controller? -- 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
