DPDK usage discussions
 help / color / mirror / Atom feed
From: "Rosen, Rami" <rami.rosen@intel.com>
To: Aaron Hughes <hughesac@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Unsupported kernel driver
Date: Tue, 14 Aug 2018 11:32:24 +0000	[thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F9675039F4@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <CAP=pv7OAiL+sOtjRByTP0e+kesJedJmCghiZ7KHaSYx-x5WE_Q@mail.gmail.com>

Hi Aaron,

What does 
dpdk-17.05/usertools/dpdk-devbind.py -s
show ?

Regards,
Rami Rosen

-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of Aaron Hughes
Sent: Tuesday, August 14, 2018 08:54
To: users@dpdk.org
Subject: [dpdk-users] Unsupported kernel driver

I'm having trouble getting testpmd to work with an Intel X710. I'm seeing an unsupported kernel driver error. Based on this page I think I'm using the correct kernel driver:

http://doc.dpdk.org/guides/nics/i40e.html#recommended-matching-list


Does anyone have any idea what I'm doing wrong?



My system info:
CentOS release 6.5 (Final)
Intel X710 with version 5.05 firmware

Kernel Driver: i40e version 1.5.23 (From Intel)

DPDK version: 17.05



/tmp/testpmd --log-level=8 -w 05:00.0EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 8 on socket 0
EAL: Detected lcore 6 as core 9 on socket 0
EAL: Detected lcore 7 as core 10 on socket 0
EAL: Detected lcore 8 as core 11 on socket 0
EAL: Detected lcore 9 as core 12 on socket 0
EAL: Detected lcore 10 as core 0 on socket 0
EAL: Detected lcore 11 as core 1 on socket 0
EAL: Detected lcore 12 as core 2 on socket 0
EAL: Detected lcore 13 as core 3 on socket 0
EAL: Detected lcore 14 as core 4 on socket 0
EAL: Detected lcore 15 as core 8 on socket 0
EAL: Detected lcore 16 as core 9 on socket 0
EAL: Detected lcore 17 as core 10 on socket 0
EAL: Detected lcore 18 as core 11 on socket 0
EAL: Detected lcore 19 as core 12 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 20 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fb9e9400000 (size = 0x200000)
EAL: Ask a virtual area of 0x7fc00000 bytes
EAL: Virtual area found at 0x7fb969600000 (size = 0x7fc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fb969200000 (size = 0x200000)
EAL: Requesting 1024 pages of size 2MB from socket 0
EAL: TSC frequency is ~2394234 KHz
EAL: Master lcore 0 is ready (tid=e9afc8c0;cpuset=[0])
EAL: lcore 10 is ready (tid=62df5700;cpuset=[10])
EAL: lcore 2 is ready (tid=67dfd700;cpuset=[2])
EAL: lcore 1 is ready (tid=687fe700;cpuset=[1])
EAL: lcore 18 is ready (tid=5dded700;cpuset=[18])
EAL: lcore 13 is ready (tid=60ff2700;cpuset=[13])
EAL: lcore 3 is ready (tid=673fc700;cpuset=[3])
EAL: lcore 6 is ready (tid=655f9700;cpuset=[6])
EAL: lcore 17 is ready (tid=5e7ee700;cpuset=[17])
EAL: lcore 9 is ready (tid=637f6700;cpuset=[9])
EAL: lcore 12 is ready (tid=619f3700;cpuset=[12])
EAL: lcore 7 is ready (tid=64bf8700;cpuset=[7])
EAL: lcore 4 is ready (tid=669fb700;cpuset=[4])
EAL: lcore 8 is ready (tid=641f7700;cpuset=[8])
EAL: lcore 14 is ready (tid=605f1700;cpuset=[14])
EAL: lcore 19 is ready (tid=5d3ec700;cpuset=[19])
EAL: lcore 16 is ready (tid=5f1ef700;cpuset=[16])
EAL: lcore 5 is ready (tid=65ffa700;cpuset=[5])
EAL: lcore 15 is ready (tid=5fbf0700;cpuset=[15])
EAL: lcore 11 is ready (tid=623f4700;cpuset=[11])
EAL: Driver (net_ark) doesn't match the device
EAL: Driver (net_avp) doesn't match the device
EAL: Driver (net_bnxt) doesn't match the device
EAL: Driver (net_cxgbe) doesn't match the device
EAL: Driver (net_e1000_igb) doesn't match the device
EAL: Driver (net_e1000_igb_vf) doesn't match the device
EAL: Driver (net_e1000_em) doesn't match the device
EAL: Driver (net_ena) doesn't match the device
EAL: Driver (net_enic) doesn't match the device
EAL: Driver (net_fm10k) doesn't match the device
EAL: PCI device 0000:05:00.0 on NUMA socket -1
EAL: probe driver: 8086:1572 net_i40e
EAL: Not managed by a supported kernel driver, skipped
EAL: Driver (net_i40e_vf) doesn't match the device
EAL: Driver (net_ixgbe) doesn't match the device
EAL: Driver (net_ixgbe_vf) doesn't match the device
EAL: Driver (net_liovf) doesn't match the device
EAL: Driver (net_nfp) doesn't match the device
EAL: Driver (net_qede) doesn't match the device
EAL: Driver (net_qede_vf) doesn't match the device
EAL: Driver (net_sfc_efx) doesn't match the device
EAL: Driver (net_thunderx) doesn't match the device
EAL: Driver (net_virtio) doesn't match the device
EAL: Driver (net_vmxnet3) doesn't match the device
EAL: Driver (event_skeleton_pci) doesn't match the device
EAL: Driver (octeontx_ssowvf) doesn't match the device
EAL: Driver (octeontx_ssovf) doesn't match the device
EAL: No probed ethernet devices

  reply	other threads:[~2018-08-14 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14  5:54 Aaron Hughes
2018-08-14 11:32 ` Rosen, Rami [this message]
2018-08-14 13:55   ` Aaron Hughes
2018-08-14 18:51     ` Rosen, Rami

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=9B0331B6EBBD0E4684FBFAEDA55776F9675039F4@HASMSX110.ger.corp.intel.com \
    --to=rami.rosen@intel.com \
    --cc=hughesac@gmail.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).