Robert Hancock wrote:
Tejun Heo wrote:
Kuan Luo wrote:
For ADMA, I lean to disable it for default because stability is more
important to our customers. At least, bug in this link:
http://www.gossamer-threads.com/lists/linux/kernel/885929 is not
resolved.
Robert, what do you think? Should we disable ADMA by default from
2.6.26-rcX?
I can't say I'm inherently in favor of it, but if people feel strongly
enough about it I won't yell too loudly. If we do disable it, I would
suggest printing out a message saying it can be enabled when the driver
loads if they didn't switch it on, in case people complain about it as a
regression otherwise.
BTW, it would be nice if NVIDIA would put some more resources into
debugging these issues so that we didn't have to take such an action.
With some of these problems, there are definite limits to what we can do
to figure out what's going on without knowing what is happening
internally in the controller.
By my reckoning the known issues are:
-Occasional timeouts when issuing the first command after switching from
NCQ to non-NCQ commands (even with the udelay() call in the driver to
partially work around this). When this happens, going into register mode
during error handling times out.
-When handling a failed command (ex: caused by a bad sector), going into
register mode times out and retrieving result taskfile from ATA
registers can cause a MCE due to a northbridge HyperTransport bus
transaction timeout (reported by Kuan, I don't think anyone else has
mentioned this one).
-Hotplug/hot-unplug fails to work properly, hotplug interrupts not
raised (seemingly only on certain boards/configurations as I can't
duplicate this problem). http://bugzilla.kernel.org/show_bug.cgi?id=8421
--
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
