public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.h.duyck@intel.com>
To: Jet Chen <jet.chen@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Dave Jiang <dave.jiang@intel.com>
Cc: fengguang.wu@intel.com, wei.w.lin@intel.com,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH] DCA: fix over-warning in ioat3_dca_init
Date: Thu, 08 May 2014 08:57:35 -0700	[thread overview]
Message-ID: <536BA96F.1030203@intel.com> (raw)
In-Reply-To: <536BA2A3.50506@intel.com>

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


  reply	other threads:[~2014-05-08 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1399542166-42985-1-git-send-email-jet.chen@intel.com>
2014-05-08 15:04 ` [PATCH] DCA: fix over-warning in ioat3_dca_init Alexander Duyck
2014-05-08 15:28   ` Jet Chen
2014-05-08 15:57     ` Alexander Duyck [this message]
2014-05-08 16:13       ` Jiang, Dave
2014-05-08 16:30         ` Jet Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=536BA96F.1030203@intel.com \
    --to=alexander.h.duyck@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=jet.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wei.w.lin@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox