public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Joshua McBeth <joshua.mcbeth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: SR-IOV with mlx4 on ConnectX-2 fails with DMAR errors
Date: Tue, 13 Dec 2016 09:54:41 -0700	[thread overview]
Message-ID: <20161213165441.GB11099@obsidianresearch.com> (raw)
In-Reply-To: <CAN27Ff74Ov8bgsZP1QJJOwvWc5_KOW_U=PsP+=Z87AJz+VSAOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Mon, Dec 12, 2016 at 10:57:58PM -0500, Joshua McBeth wrote:
> Regarding this issue, I discovered earlier kernels were working with
> SR-IOV enabled and bisected to the commit
> 4be90bc60df47f6268b594c4fb6c90f0ff2f519f ("IB/mad: Remove
> ib_get_dma_mr calls").
> 
> However, this commit seems to be part of a larger refactoring patch
> set and reverting just this commit does not resolve the DMAR errors
> nor enable the 'ib0' interface to function.

?? if you bisected correctly then reverting the ID'd patch should
solve the problem.

Jason

--
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

  parent reply	other threads:[~2016-12-13 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 16:04 SR-IOV with mlx4 on ConnectX-2 fails with DMAR errors Joshua McBeth
     [not found] ` <CAN27Ff4RYh3y_45PUxxXhGuDvrrrjm8qe38fj5JPq7oV2QmdYA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13  3:57   ` Joshua McBeth
     [not found]     ` <CAN27Ff74Ov8bgsZP1QJJOwvWc5_KOW_U=PsP+=Z87AJz+VSAOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 16:54       ` Jason Gunthorpe [this message]
     [not found]         ` <20161213165441.GB11099-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-12-13 18:36           ` Joshua McBeth
     [not found]             ` <CAN27Ff7hEr4u5nyELjwRXb3W_t0TNefuuT4AzdjAoWWGRHqTFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 19:01               ` Jason Gunthorpe
     [not found]                 ` <20161213190102.GA15119-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-12-14 15:06                   ` Joshua McBeth
     [not found]                     ` <CAN27Ff4P_11FQ-VuiPcL4S67uVh4xSJpqyZ0Q4AbPfd64fmO9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-14 22:38                       ` Jason Gunthorpe

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=20161213165441.GB11099@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=joshua.mcbeth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox