From: "Masafumi OE" <masa@fumi.org>
To: "'Masaru Oki'" <m-oki@stratosphere.co.jp>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Intel X552/557 is not working.
Date: Mon, 8 Jun 2015 15:45:02 +0900 [thread overview]
Message-ID: <002101d0a1b6$a5e0fe50$f1a2faf0$@fumi.org> (raw)
In-Reply-To: <CAFLKUzKLcC9vDK5i7CHoPL27UrHM+UnREz9szwW-dxySuzNpbA@mail.gmail.com>
Great!
I will try it.
Regards,
--
Masafumi OE, NAOJ
-----Original Message-----
From: Masaru Oki [mailto:m-oki@stratosphere.co.jp]
Sent: Monday, June 8, 2015 11:32 AM
To: Masafumi OE
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] Intel X552/557 is not working.
Hi,
I made (unofficial, quick) patch. The code is mostly pulled from FreeBSD.
My Ubuntu 14.04 on X10SDV-TLN4F is works fine.
http://www.e-neta.jp/~oki/dpdk-ixgbe.diff
2015-06-08 11:19 GMT+09:00 Masafumi OE <masa@fumi.org>:
> Hi,
>
> I'm trying to use X552/X557-AT 10GBASE-T NIC on Xeon-D 1540. However
> it did not work properly.
> Binding X552/557to PMD for ixgbe is fine but testpmd is not working on
> X552/557 because th_ixgbe_dev_init() return Hardware Initialization
> Failure:-3.
>
> Do you have any idea?
>
> --
> Supermicro X10SDV-TLN4F
> Running on CentOS 7.0:
> DPDK is getting via git.
> --
> $ lspci -nn | grep X55
> 03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet
> Connection X552/X557-AT 10GBASE-T [8086:15ad]
> 03:00.1 Ethernet controller [0200]: Intel Corporation Ethernet
> Connection X552/X557-AT 10GBASE-T [8086:15ad]
>
> $ ./dpdk_nic_bind.py --status
>
> Network devices using DPDK-compatible driver
> ============================================
> 0000:03:00.0 'Ethernet Connection X552/X557-AT 10GBASE-T'
> drv=uio_pci_generic unused=vfio-pci
> 0000:03:00.1 'Ethernet Connection X552/X557-AT 10GBASE-T'
> drv=uio_pci_generic unused=vfio-pci
>
> Network devices using kernel driver
> ===================================
> 0000:05:00.0 'I350 Gigabit Network Connection' if=eno1 drv=igb
> unused=vfio-pci,uio_pci_generic *Active*
> 0000:05:00.1 'I350 Gigabit Network Connection' if=eno2 drv=igb
> unused=vfio-pci,uio_pci_generic
>
> Other network devices
> =====================
> <none>
>
> --
> $ sudo -s app/testpmd -c 300 -n 4 -- -i --burst=32 --rxfreet=32
> --mbcache=250 --txpt=32 --rxht=8 --rxwt=0 --txfreet=32 --txrst=32
> --txqflags=0xf01
> EAL: 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 5 on socket 0
> EAL: Detected lcore 6 as core 6 on socket 0
> EAL: Detected lcore 7 as core 7 on socket 0
> EAL: Detected lcore 8 as core 0 on socket 0
> EAL: Detected lcore 9 as core 1 on socket 0
> EAL: Detected lcore 10 as core 2 on socket 0
> EAL: Detected lcore 11 as core 3 on socket 0
> EAL: Detected lcore 12 as core 4 on socket 0
> EAL: Detected lcore 13 as core 5 on socket 0
> EAL: Detected lcore 14 as core 6 on socket 0
> EAL: Detected lcore 15 as core 7 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 16 lcore(s)
> EAL: VFIO modules not all loaded, skip VFIO support...
> EAL: Setting up memory...
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff893200000 (size = 0x200000)
> EAL: Ask a virtual area of 0xc00000 bytes
> EAL: Virtual area found at 0x7ff892400000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x7000000 bytes
> EAL: Virtual area found at 0x7ff88b200000 (size = 0x7000000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7ff88ae00000 (size = 0x200000)
> EAL: Requesting 64 pages of size 2MB from socket 0
> ^NEAL: TSC frequency is ~2000000 KHz
> EAL: Master lcore 8 is ready (tid=9472d900;cpuset=[8])
> EAL: lcore 9 is ready (tid=8a5fe700;cpuset=[9])
> EAL: PCI device 0000:03:00.0 on NUMA socket 0
> EAL: probe driver: 8086:15ad rte_ixgbe_pmd
> EAL: PCI memory mapped at 0x7ff893000000
> EAL: PCI memory mapped at 0x7ff8946f3000
> PMD: eth_ixgbe_dev_init(): Hardware Initialization Failure: -3
> EAL: Error - exiting with code: 1
> Cause: Requested device 0000:03:00.0 cannot be used
>
> --
> Masafumi OE, NAOJ
>
>
next prev parent reply other threads:[~2015-06-08 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 2:19 Masafumi OE
2015-06-08 2:32 ` Masaru Oki
2015-06-08 6:45 ` Masafumi OE [this message]
2015-06-11 6:41 ` Lu, Wenzhuo
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='002101d0a1b6$a5e0fe50$f1a2faf0$@fumi.org' \
--to=masa@fumi.org \
--cc=dev@dpdk.org \
--cc=m-oki@stratosphere.co.jp \
/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).