From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Sebastian Riemer
<sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: IB/iSER problems with Linux 3.0
Date: Tue, 17 Jan 2012 16:56:13 +0200 [thread overview]
Message-ID: <4F158C0D.7070302@mellanox.com> (raw)
In-Reply-To: <4F154CF2.7030504-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
On 1/17/2012 12:26 PM, Sebastian Riemer wrote:
> In the log from working iSER there is the RDMA mapping debug message
> at the position of the error in the other log
I didn't understand that comment, please clarify, anyway, could you try
and patch your 3.0.15 kernel with commit
52439540ea30396982b69662dd21aede6b336288 "IB/iser: DMA unmap TX bufs
used for iSCSI/iSER headers" from upstream, this could help here.
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-17 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 21:16 IB/iSER problems with Linux 3.0 Or Gerlitz
[not found] ` <CAJZOPZL=bV4SjdD2eakX9MhOhw=91xzCK=BEkirhRQd8oPA6bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-17 10:26 ` Sebastian Riemer
[not found] ` <4F154CF2.7030504-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2012-01-17 14:56 ` Or Gerlitz [this message]
[not found] ` <4F158C0D.7070302-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-01-19 11:29 ` Sebastian Riemer
[not found] ` <4F17FE97.6090708-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2012-01-19 12:18 ` Or Gerlitz
[not found] ` <4F1809FC.2020908-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-01-19 13:56 ` Solved: " Sebastian Riemer
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=4F158C0D.7070302@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.