From: Dave Jiang <dave.jiang@intel.com>
To: Jon Mason <jdmason@kudzu.us>, perplexus <perplexus@ya.ru>,
linux-ntb@googlegroups.com
Subject: Re: Problem with ntb_transport + ntb_netdev
Date: Tue, 10 Jan 2017 15:24:15 -0700 [thread overview]
Message-ID: <7784bee8-663d-bd89-2d2b-ef47081153d1@intel.com> (raw)
In-Reply-To: <CAPoiz9zYa19b1fHVJFvmM-qrNigXkxDTvV3Hrjc81H0tfaMPKA@mail.gmail.com>
On 01/10/2017 03:03 PM, Jon Mason wrote:
> Adding the NTB mailing list
>
> On Mon, Jan 9, 2017 at 11:27 AM, perplexus <perplexus@ya.ru> wrote:
>> Hello.
>>
>> I'm working with NTB (kernel version 4.10) on Xeon D-1527 CPU and have a problem with couple ntb_transport + ntb_netdev.
>>
>> On the local side I run:
>> sudo /etc/init.d/irqbalance stop
>> sudo modprobe ntb_transport dyndbg=+p
>> sudo modprobe ntb_netdev dyndbg=+p
>> sudo ifconfig eth0 192.168.1.1 up
>>
>> On the remote side I run:
>> sudo /etc/init.d/irqbalance stop
>> sudo modprobe ntb_transport dyndbg=+p
>> sudo modprobe ntb_netdev dyndbg=+p
>> sudo ifconfig eth0 192.168.1.2 up
>>
>> Along with these steps I run ping 192.168.1.2 and get about 2-3 successfull transmitted/received packets then get 'Destination host unreacheble'.
>>
>
> Do pings in the other direction work?
>
How are the NTBs connected? Where did the get the hardware? Also can you
dump the stats in debugfs? And which distro are you running? Sometimes
Network Manager will yank the IP for no reason if you don't configure it
correctly and thus your interface can't route.
next prev parent reply other threads:[~2017-01-10 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <360341483979222@web10o.yandex.ru>
2017-01-10 22:03 ` Problem with ntb_transport + ntb_netdev Jon Mason
2017-01-10 22:24 ` Dave Jiang [this message]
2017-01-11 10:08 ` shlemisto
2017-01-11 15:27 ` shlemisto
2017-01-11 16:42 ` Dave Jiang
2017-01-11 16:45 ` Dave Jiang
2017-01-12 10:28 ` shlemisto
2017-01-12 15:29 ` shlemisto
2017-01-12 16:37 ` Dave Jiang
2017-01-12 16:58 ` shlemisto
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=7784bee8-663d-bd89-2d2b-ef47081153d1@intel.com \
--to=dave.jiang@intel.com \
--cc=jdmason@kudzu.us \
--cc=linux-ntb@googlegroups.com \
--cc=perplexus@ya.ru \
/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