linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: rdma link add NAME type rxe netdev IFACE stopped working
Date: Thu, 2 Sep 2021 10:02:13 -0300	[thread overview]
Message-ID: <20210902130213.GT1200268@ziepe.ca> (raw)
In-Reply-To: <b4a1e866-95ed-7bf1-f9da-bca5700db7e1@gmail.com>

On Wed, Sep 01, 2021 at 10:25:25PM -0500, Bob Pearson wrote:
> On 9/1/21 10:04 PM, Bob Pearson wrote:
> > rdma link has started to fail today reporting an error as follows after working before.
> > 
> > bob@ubunto-21:~$ sudo rdma link add rxe0 type rxe netdev enp0s3
> > 
> > error: Invalid argument
> > 
> > bob@ubunto-21:
> > 
> > Nothing has changed in the past day or two except I pulled recent changes into rdma-core. This runs after
> > typing
> > 
> > export LD_LIBRARY_PATH=/home/bob/src/rdma-core/build/lib/:/usr/local/lib:/usr/lib
> > 
> > which is also the same. Any ideas?
> > 
> > Bob
> > 
> 
> Update. I then recompiled the kernel after pulling latest changes
> and now it works. In theory this shouldn't be necessary. The kernel
> APIs should be beckwards compatible.

I don't think anything has changed here in a long time, so I have no
guess

'rdma link' has no relation to rdma-core either

Perhaps your kernel got in a bad state?

Jason

  reply	other threads:[~2021-09-02 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f1c73298-b37f-8589-bdb1-a727c3b7c844@gmail.com>
2021-09-02  3:22 ` Fwd: rdma link add NAME type rxe netdev IFACE stopped working Bob Pearson
2021-09-02  3:25 ` Bob Pearson
2021-09-02 13:02   ` Jason Gunthorpe [this message]
2021-09-02 19:49     ` Bob Pearson

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=20210902130213.GT1200268@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=zyjzyj2000@gmail.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;
as well as URLs for NNTP newsgroup(s).