Messages in this thread | | | Date | Sat, 10 Feb 2007 09:34:46 +0000 | From | David R <> | Subject | Re: sata_nv - ADMA issues with 2.6.20 |
| |
Robert Hancock wrote:
> So it was tag 0 that timed out , and according to the CPBs the > controller indeed believes the command is still outstanding, i.e. we > didn't lose an interrupt. I'm suspicious of the fact that only one of > two identical drives produced this error.. some kind of hardware-related > problem perhaps? 30 seconds is an awfully long time for a drive to take
That was my first thought. Maybe the drive has some fault that only shows up with NCQ in use. I'll keep an eye on it.
> You can also try disabling NCQ without disabling ADMA and see what that > does: > > echo 1 > /sys/block/sdX/device/queue_depth
I'll give this a go when I next reboot.
Thanks David
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |