lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <536BA96F.1030203@intel.com>
Date:	Thu, 08 May 2014 08:57:35 -0700
From:	Alexander Duyck <alexander.h.duyck@...el.com>
To:	Jet Chen <jet.chen@...el.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Dave Jiang <dave.jiang@...el.com>
CC:	fengguang.wu@...el.com, wei.w.lin@...el.com,
	linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org
Subject: Re: [PATCH] DCA: fix over-warning in ioat3_dca_init

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.

Thanks,

Alex

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ