DPDK usage discussions
 help / color / mirror / Atom feed
From: Michal Michalowski <michalm@openet.com>
To: "Hunt, David" <david.hunt@intel.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] OS hang when running helloworld example with two I210 NICs
Date: Wed, 22 Mar 2017 14:38:50 +0000	[thread overview]
Message-ID: <5B7D1E64EC96F04199B0FF4AEBA738120115A35F@DUBEXCH02.openet-dublin> (raw)
In-Reply-To: <5B7D1E64EC96F04199B0FF4AEBA738120115A35E@DUBEXCH02.openet-dublin>

Hi Dave,

I have tried your suggestion and it works if one NIC is x16 and the other in x4.

Thanks again,
Michal
________________________________________
From: users [users-bounces@dpdk.org] On Behalf Of Michal Michalowski [michalm@openet.com]
Sent: 21 March 2017 16:05
To: Hunt, David; users@dpdk.org
Subject: Re: [dpdk-users] OS hang when running helloworld example with two I210 NICs

Hi Dave,

Yes this is pretty old box. I'll try your suggestion as soon as I get x1 graphics card and let you know.

Thanks for help.

Michal




________________________________________
From: Hunt, David [david.hunt@intel.com]
Sent: 21 March 2017 15:46
To: Michal Michalowski; users@dpdk.org
Subject: Re: [dpdk-users] OS hang when running helloworld example with two I210 NICs

On 21/3/2017 1:52 PM, Michal Michalowski wrote:

> Hi,
>
> I do not use any PCI riser or multiplexer. I have 4 PCIe slots.
> 1) PCIe x1           -    NIC1 (24:00)
> 2) PCIe x16         -    Graphics card
> 3) PCIe x1           -    disabled
> 4) PCIe x4           -   NIC2 (18:00)
>
>
> Output of lscpi is:
> michal@michal-HP-Z200-Workstation:~$ sudo lspci -t
> -+-[0000:3f]-+-00.0
>   |           +-00.1
>   |           +-02.0
>   |           +-02.1
>   |           +-03.0
>   |           +-03.1
>   |           +-03.2
>   |           +-03.4
>   |           +-04.0
>   |           +-04.1
>   |           +-04.2
>   |           +-04.3
>   |           +-05.0
>   |           +-05.1
>   |           +-05.2
>   |           \-05.3
>   \-[0000:00]-+-00.0
>               +-03.0-[01]--+-00.0
>               |            \-00.1
>               +-08.0
>               +-08.1
>               +-08.2
>               +-08.3
>               +-10.0
>               +-10.1
>               +-16.0
>               +-16.3
>               +-19.0
>               +-1a.0
>               +-1b.0
>               +-1c.0-[18]----00.0
>               +-1c.4-[24]----00.0
>               +-1d.0
>               +-1e.0-[10]----00.0
>               +-1f.0
>               \-1f.2
>
> Cheers,
> Michal

Michal,
    Looks OK to me. At this point I don't know what's causing your
issue. And it's likely that if you switched those NICs into a more
modern server (the Z200 is quite old at this stage), it's likely that
everything would just work. All I can suggest at this stage is to maybe
get your hands on a PCIe x1 GFX card to free up the x16 slot, and try
using the gen2 x16 and the x4 for the NICs.
Dave.



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation, retention or transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited and may be unlawful. If you have received this e-mail or any file or attachment transmitted with it in error please notify postmaster@openet.com. Although Openet has taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation, retention or transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited and may be unlawful. If you have received this e-mail or any file or attachment transmitted with it in error please notify postmaster@openet.com. Although Openet has taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

  reply	other threads:[~2017-03-22 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 16:55 Michal Michalowski
2017-03-21 12:19 ` Hunt, David
2017-03-21 12:46   ` Michal Michalowski
2017-03-21 13:17     ` Hunt, David
2017-03-21 13:52       ` Michal Michalowski
2017-03-21 14:46         ` Hunt, David
2017-03-21 15:05           ` Michal Michalowski
2017-03-22 14:38             ` Michal Michalowski [this message]
2017-03-21 13:59       ` Hunt, David
2017-03-21 14:01         ` Hunt, David

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=5B7D1E64EC96F04199B0FF4AEBA738120115A35F@DUBEXCH02.openet-dublin \
    --to=michalm@openet.com \
    --cc=david.hunt@intel.com \
    --cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).