From: Eyal Perry <eyalpe@dev.mellanox.co.il>
To: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: Amir Vadai <amirv@mellanox.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: mlx4_core: DMA-API: device driver tries to sync DMA memory it has not allocated
Date: Wed, 5 Mar 2014 18:25:52 +0200 [thread overview]
Message-ID: <20140305162534.GA19488@mtl-eit-vdi-146.mtl.labs.mlnx> (raw)
In-Reply-To: <20140303185832.67862975@thinkpad>
On 03/03/14 18:58 +0100, Gerald Schaefer wrote:
> I checked again with 3.10 and 3.11, and couldn't reproduce the warning
> there. However, there is another warning on those kernel versions:
>
> mlx4_core 0000:00:00.0: DMA-API: device driver failed to check map error[device address=0x00000001046af186] [size=258 bytes] [mapped as single]
>
> That one was fixed with commit 237a3a3b "net/mlx4_en: Fix handling of dma_map failure".
> When I apply commit 237a3a3b on top of 3.11, I can also reproduce the
> new "sync DMA" warning there.
>
> So, either the new "sync DMA" warning was introduced with commit 237a3a3b,
> or it was just occluded by the previous "map error" warning.
Hi Gerald,
Thanks for the update and for your efforts on investigating this issue,
we are currently working on reproducing this issue on our lab in order
to understand thoroughly the root cause.
Eyal
prev parent reply other threads:[~2014-03-05 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 13:44 Gerald Schaefer
2014-02-27 17:01 ` Amir Vadai
2014-02-28 21:24 ` Gerald Schaefer
[not found] ` <20140302084046.GD809@mtl-eit-vdi-22.mtl.labs.mlnx>
2014-03-03 17:58 ` Gerald Schaefer
2014-03-05 16:25 ` Eyal Perry [this message]
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=20140305162534.GA19488@mtl-eit-vdi-146.mtl.labs.mlnx \
--to=eyalpe@dev.mellanox.co.il \
--cc=amirv@mellanox.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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®