On 05/09/2014 12:13 AM, Jiang, Dave wrote: > On Thu, 2014-05-08 at 08:57 -0700, Alexander Duyck wrote: >> On 05/08/2014 08:28 AM, Jet Chen wrote: >>> I agree with your option that it is a real BIOS bug and it puts pressure on the BIOS guys to get this fixed. However, this warning message interferes with our kernel booting tests and kernel performance tests. We have to disable CONFIG_INTEL_IOATDMA in kconfig until this issue gets fixed. Before that, code of CONFIG_INTEL_IOATDMA will not be validated in our testing system :(. >>> Hope this issue could get fixed soon. >>> >>> Thanks, >>> Jet >>> >> >> First I would recommend updating your BIOS. If the updated BIOS also >> has the issue I would recommend taking this feedback to whoever provided >> the BIOS for your platform so that they can implement the fix. >> >> If I am not mistaken some BIOSes have the option to disable DCA and/or >> IOATDMA. You might want to check yours to see if you can just disable >> DCA on your platform until the issue can be resolved. > > Disabling DCA is the preferred option. IOATDMA is functional without > DCA. > > Jet, > What exactly are you attempting to test with IOATDMA? The only two > consumers of this DMA driver I know of are MDRAID and NTB. But support > for XOR/PQ ops on Xeon platforms have been removed due to various > reasons recently so it really is just NTB at the moment in the latest > kernels. We are running LKP to test kernel boot and performance. More information you can find at https://01.org/lkp/ This issue shows up in our boot testing with certain kconfig and impacts many of our test machines. It is difficult to update BIOS for all test boxes. Besides, we still not make sure every test box model have a workable version of BIOS. We will consider disabling DCA as your suggestion. Thanks, Jet > >> Thanks, >> >> Alex >> -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
