From: Dan Williams <dan.j.williams@intel.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Sosnowski, Maciej" <maciej.sosnowski@intel.com>
Subject: Re: 2.6.32-rc2: Intel(R) I/OAT DMA Engine init failed
Date: Mon, 05 Oct 2009 15:00:56 -0700 [thread overview]
Message-ID: <1254780056.8066.6.camel@dwillia2-linux.ch.intel.com> (raw)
In-Reply-To: <a4423d670910020246n1e82644bud8b7a01d49b93e26@mail.gmail.com>
On Fri, 2009-10-02 at 02:46 -0700, Alexander Beregalov wrote:
> Hi
> The kerneil is 2.6.32-rc2-00196-g0efe5e3.
> Should I bisect?
>
> ioatdma: Intel(R) QuickData Technology Driver 4.00
> ioatdma 0000:00:08.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> ioatdma 0000:00:08.0: setting latency timer to 64
> alloc irq_desc for 33 on node -1
> alloc kstat_irqs on node -1
> ioatdma 0000:00:08.0: irq 33 for MSI/MSI-X
> ioatdma 0000:00:08.0: Self-test copy timed out, disabling
> ioatdma 0000:00:08.0: Intel(R) I/OAT DMA Engine init failed
I may ask for a bisect later, but for now let's try and see why it is
failing. It is something platform specific as 2.6.32-rc3 loads fine on
my v1.2 platform. Please reproduce this with the patch below.
Thanks,
Dan
diff --git a/drivers/dma/ioat/dma.c b/drivers/dma/ioat/dma.c
index c524d36..8f807b4 100644
--- a/drivers/dma/ioat/dma.c
+++ b/drivers/dma/ioat/dma.c
@@ -24,6 +24,7 @@
* This driver supports an Intel I/OAT DMA engine, which does asynchronous
* copy operations.
*/
+#define DEBUG
#include <linux/init.h>
#include <linux/module.h>
@@ -815,6 +816,7 @@ int __devinit ioat_dma_self_test(struct ioatdma_device *device)
struct completion cmp;
unsigned long tmo;
unsigned long flags;
+ enum dma_status stat;
src = kzalloc(sizeof(u8) * IOAT_TEST_SIZE, GFP_KERNEL);
if (!src)
@@ -864,10 +866,10 @@ int __devinit ioat_dma_self_test(struct ioatdma_device *device)
tmo = wait_for_completion_timeout(&cmp, msecs_to_jiffies(3000));
- if (tmo == 0 ||
- dma->device_is_tx_complete(dma_chan, cookie, NULL, NULL)
- != DMA_SUCCESS) {
- dev_err(dev, "Self-test copy timed out, disabling\n");
+ stat = dma->device_is_tx_complete(dma_chan, cookie, NULL, NULL);
+ if (tmo == 0 || stat != DMA_SUCCESS) {
+ dev_err(dev, "Self-test copy timed out, disabling %ld:%d\n",
+ tmo, stat);
err = -ENODEV;
goto free_resources;
}
next prev parent reply other threads:[~2009-10-05 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 9:46 Alexander Beregalov
2009-10-05 22:00 ` Dan Williams [this message]
2009-10-06 10:54 ` Alexander Beregalov
2009-10-13 1:48 ` Dan Williams
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=1254780056.8066.6.camel@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@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
all inboxes | Powered by JetHome®