DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev]  I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
@ 2015-10-14  1:29 최익성
  2015-10-14  1:38 ` Xu, Qian Q
  2015-10-14  1:49 ` 최익성
  0 siblings, 2 replies; 9+ messages in thread
From: 최익성 @ 2015-10-14  1:29 UTC (permalink / raw)
  To: dev

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 12720 bytes --]

Dear DPDK experts.
 
Thank you very much for your best great efforts and precious answers.
 
I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug).
 
My problem is that I cannot receive any traffics in test-pmd.
 
There are 2 nics (2 port NIC), I connected port 0 to port 1(loopback), port 2 to port3 (loopback).
 
I attached details of my setup. I also attached my DPDK setup shell script.
 
Did I miss something? or Is there any my mistakes?
 
 
I will really appreciate if you check them and I can be given any advice and answers.
 
 
It is important for me and urgent job.
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.
 
 
* test-pmd log.
 
 
$ sudo ./build/app/testpmd -c 0xF -n 4 -- -i --portmask=0xF --nb-cores=3
 
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 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 1
EAL: Detected lcore 11 as core 1 on socket 1
EAL: Detected lcore 12 as core 2 on socket 1
EAL: Detected lcore 13 as core 3 on socket 1
EAL: Detected lcore 14 as core 4 on socket 1
EAL: Detected lcore 15 as core 8 on socket 1
EAL: Detected lcore 16 as core 9 on socket 1
EAL: Detected lcore 17 as core 10 on socket 1
EAL: Detected lcore 18 as core 11 on socket 1
EAL: Detected lcore 19 as core 12 on socket 1
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 0x1000000 bytes
EAL: Virtual area found at 0x7f85eb000000 (size = 0x1000000)
EAL: Ask a virtual area of 0x3800000 bytes
EAL: Virtual area found at 0x7f85e7600000 (size = 0x3800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f85e7200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f85e6e00000 (size = 0x200000)
EAL: Ask a virtual area of 0xfb400000 bytes
EAL: Virtual area found at 0x7f84eb800000 (size = 0xfb400000)
EAL: Ask a virtual area of 0xffc00000 bytes
EAL: Virtual area found at 0x7f83eba00000 (size = 0xffc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f83eb600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f83eb200000 (size = 0x200000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: Requesting 2048 pages of size 2MB from socket 1
EAL: TSC frequency is ~2793267 KHz
EAL: Master lcore 0 is ready (tid=ee4a0940;cpuset=[0])
EAL: lcore 3 is ready (tid=ea1cf700;cpuset=[3])
EAL: lcore 2 is ready (tid=ecc69700;cpuset=[2])
EAL: lcore 1 is ready (tid=ed46a700;cpuset=[1])
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec000000
EAL:   PCI memory mapped at 0x7f85ec080000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec084000
EAL:   PCI memory mapped at 0x7f85ec104000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 1 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.0 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec108000
EAL:   PCI memory mapped at 0x7f85ec188000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 2 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.1 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec18c000
EAL:   PCI memory mapped at 0x7f85ec20c000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 3 vendorID=0x8086 deviceID=0x10fb
Interactive-mode selected
Configuring Port 0 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f8a5c0 hw_ring=0x7f85e6f8c600 dma_addr=0x6c158c600
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f79cc0 sw_sc_ring=0x7f85e6f79780 hw_ring=0x7f85e6f7a200 dma_addr=0x6c157a200
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 0: 90:E2:BA:8B:BF:C0
Configuring Port 1 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f674c0 hw_ring=0x7f85e6f69500 dma_addr=0x6c1569500
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f56bc0 sw_sc_ring=0x7f85e6f56680 hw_ring=0x7f85e6f57100 dma_addr=0x6c1557100
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 1: 90:E2:BA:8B:BF:C1
Configuring Port 2 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f443c0 hw_ring=0x7f85e6f46400 dma_addr=0x6c1546400
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f33ac0 sw_sc_ring=0x7f85e6f33580 hw_ring=0x7f85e6f34000 dma_addr=0x6c1534000
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 2: 90:E2:BA:8B:B8:CC
Configuring Port 3 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f212c0 hw_ring=0x7f85e6f23300 dma_addr=0x6c1523300
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f109c0 sw_sc_ring=0x7f85e6f10480 hw_ring=0x7f85e6f10f00 dma_addr=0x6c1510f00
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 3: 90:E2:BA:8B:B8:CD
Checking link statuses...
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Up - speed 10000 Mbps - full-duplex
Port 2 Link Up - speed 10000 Mbps - full-duplex
Port 3 Link Up - speed 10000 Mbps - full-duplex
Done
 
 
testpmd> show port stats all
  ######################## NIC statistics for port 0  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 5
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 1  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 3
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 2  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 4
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 3  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 3
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
 
testpmd> start tx_first  io packet forwarding - CRC stripping disabled - packets/burst=32
  nb forwarding cores=3 - nb forwarding ports=4
  RX queues=1 - RX desc=128 - RX free threshold=32
  RX threshold registers: pthresh=8 hthresh=8 wthresh=0
  TX queues=1 - TX desc=512 - TX free threshold=32
  TX threshold registers: pthresh=32 hthresh=0 wthresh=0
  TX RS bit threshold=32 - TXQ flags=0xf01
 
 
testpmd> 
testpmd> 
testpmd> 
testpmd> stop
 
Telling cores to stop...
Waiting for lcores to finish...
 
  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 5
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 1  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 3
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 2  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 4
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 3  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 3
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Done.
 
 
testpmd> quitStopping port 0...done
Stopping port 1...done
Stopping port 2...done
Stopping port 3...done
bye...
 
 
 
 
* Port setup.
 
Network devices using DPDK-compatible driver
============================================
0000:09:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:09:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:81:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:81:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
 
Network devices using kernel driver
===================================
0000:04:00.0 'I350 Gigabit Network Connection' if=em1 drv=igb unused=igb_uio,vfio-pci *Active*
0000:04:00.1 'I350 Gigabit Network Connection' if=em2 drv=igb unused=igb_uio,vfio-pci 
0000:04:00.2 'I350 Gigabit Network Connection' if=em3 drv=igb unused=igb_uio,vfio-pci 
0000:04:00.3 'I350 Gigabit Network Connection' if=em4 drv=igb unused=igb_uio,vfio-pci
 
Other network devices
=====================
<none>
 
 
* I used 2048 for NUMA node 0, 2048 for NUMA node 1.
 
/proc/meminfo file.
HugePages_Total:    4096
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
 
* Fedora OS version : Fedora release 20 (Heisenbug)
 
* gcc version : gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7).
 
* Intel(R) Xeon(R) CPU E5-2680  10 cores, 64G bytes system memory.
* 2 2-port NIC cards, Intel® 82599ES 10 Gigabit Ethernet 2 port Controller. SFI/SFP+. optical link. Hence there are 4 10 GbE ports.
 
* I attached DPDK setup script in my environment.
 
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.

\x16º&šé\x1aÁ¨ zW(Ž•žtç-׍7ߍøÛMyEën®sÚ¶\x19®‘¬\x1aŠ\a¥rˆéEç\x1eŠ÷~º&™¨¥¥­\x1fãh(¢	^r‰¦j)ikGøÚ
(‚Wœ¢m´÷ÎvÛN6o'ivJ+€ú,µø±Â+a\x11#\x13>'t÷ ƒð05~ŠÝz÷ivJ+g×ƒœ·m5çM÷ã~>Óm4\bD“Eç\x1eŠ÷o*ZuÉýÂ+aHÄω×'öÊ:ç]8ïzZwgè­×¯v—d¢¸\x13¹íw9ËvÓ^uó~7ßNôÐðÓ\j(‚Wƒ(ƒ\x12Š	Ú¶êÞ

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-14  1:29 [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r 최익성
@ 2015-10-14  1:38 ` Xu, Qian Q
  2015-10-14  1:49 ` 최익성
  1 sibling, 0 replies; 9+ messages in thread
From: Xu, Qian Q @ 2015-10-14  1:38 UTC (permalink / raw)
  To: ???, dev

What's your NIC? 

Thanks
Qian

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ???
Sent: Wednesday, October 14, 2015 9:29 AM
To: dev@dpdk.org
Subject: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r

Dear DPDK experts.
 
Thank you very much for your best great efforts and precious answers.
 
I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug).
 
My problem is that I cannot receive any traffics in test-pmd.
 
There are 2 nics (2 port NIC), I connected port 0 to port 1(loopback), port 2 to port3 (loopback).
 
I attached details of my setup. I also attached my DPDK setup shell script.
 
Did I miss something? or Is there any my mistakes?
 
 
I will really appreciate if you check them and I can be given any advice and answers.
 
 
It is important for me and urgent job.
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.
 
 
* test-pmd log.
 
 
$ sudo ./build/app/testpmd -c 0xF -n 4 -- -i --portmask=0xF --nb-cores=3
 
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 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 1
EAL: Detected lcore 11 as core 1 on socket 1
EAL: Detected lcore 12 as core 2 on socket 1
EAL: Detected lcore 13 as core 3 on socket 1
EAL: Detected lcore 14 as core 4 on socket 1
EAL: Detected lcore 15 as core 8 on socket 1
EAL: Detected lcore 16 as core 9 on socket 1
EAL: Detected lcore 17 as core 10 on socket 1
EAL: Detected lcore 18 as core 11 on socket 1
EAL: Detected lcore 19 as core 12 on socket 1
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 0x1000000 bytes
EAL: Virtual area found at 0x7f85eb000000 (size = 0x1000000)
EAL: Ask a virtual area of 0x3800000 bytes
EAL: Virtual area found at 0x7f85e7600000 (size = 0x3800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f85e7200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f85e6e00000 (size = 0x200000)
EAL: Ask a virtual area of 0xfb400000 bytes
EAL: Virtual area found at 0x7f84eb800000 (size = 0xfb400000)
EAL: Ask a virtual area of 0xffc00000 bytes
EAL: Virtual area found at 0x7f83eba00000 (size = 0xffc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f83eb600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f83eb200000 (size = 0x200000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: Requesting 2048 pages of size 2MB from socket 1
EAL: TSC frequency is ~2793267 KHz
EAL: Master lcore 0 is ready (tid=ee4a0940;cpuset=[0])
EAL: lcore 3 is ready (tid=ea1cf700;cpuset=[3])
EAL: lcore 2 is ready (tid=ecc69700;cpuset=[2])
EAL: lcore 1 is ready (tid=ed46a700;cpuset=[1])
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec000000
EAL:   PCI memory mapped at 0x7f85ec080000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec084000
EAL:   PCI memory mapped at 0x7f85ec104000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 1 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.0 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec108000
EAL:   PCI memory mapped at 0x7f85ec188000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 2 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.1 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec18c000
EAL:   PCI memory mapped at 0x7f85ec20c000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 3 vendorID=0x8086 deviceID=0x10fb Interactive-mode selected Configuring Port 0 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f8a5c0 hw_ring=0x7f85e6f8c600 dma_addr=0x6c158c600
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f79cc0 sw_sc_ring=0x7f85e6f79780 hw_ring=0x7f85e6f7a200 dma_addr=0x6c157a200
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 0: 90:E2:BA:8B:BF:C0
Configuring Port 1 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f674c0 hw_ring=0x7f85e6f69500 dma_addr=0x6c1569500
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f56bc0 sw_sc_ring=0x7f85e6f56680 hw_ring=0x7f85e6f57100 dma_addr=0x6c1557100
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 1: 90:E2:BA:8B:BF:C1
Configuring Port 2 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f443c0 hw_ring=0x7f85e6f46400 dma_addr=0x6c1546400
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f33ac0 sw_sc_ring=0x7f85e6f33580 hw_ring=0x7f85e6f34000 dma_addr=0x6c1534000
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 2: 90:E2:BA:8B:B8:CC
Configuring Port 3 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f212c0 hw_ring=0x7f85e6f23300 dma_addr=0x6c1523300
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f109c0 sw_sc_ring=0x7f85e6f10480 hw_ring=0x7f85e6f10f00 dma_addr=0x6c1510f00
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 3: 90:E2:BA:8B:B8:CD
Checking link statuses...
Port 0 Link Up - speed 10000 Mbps - full-duplex Port 1 Link Up - speed 10000 Mbps - full-duplex Port 2 Link Up - speed 10000 Mbps - full-duplex Port 3 Link Up - speed 10000 Mbps - full-duplex Done
 
 
testpmd> show port stats all
  ######################## NIC statistics for port 0  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 5
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 1  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 3
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 2  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 4
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 3  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 3
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
 
testpmd> start tx_first  io packet forwarding - CRC stripping disabled - packets/burst=32
  nb forwarding cores=3 - nb forwarding ports=4
  RX queues=1 - RX desc=128 - RX free threshold=32
  RX threshold registers: pthresh=8 hthresh=8 wthresh=0
  TX queues=1 - TX desc=512 - TX free threshold=32
  TX threshold registers: pthresh=32 hthresh=0 wthresh=0
  TX RS bit threshold=32 - TXQ flags=0xf01
 
 
testpmd>
testpmd>
testpmd>
testpmd> stop
 
Telling cores to stop...
Waiting for lcores to finish...
 
  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 5
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 1  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 3
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 2  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 4
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 3  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 3
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Done.
 
 
testpmd> quitStopping port 0...done
Stopping port 1...done
Stopping port 2...done
Stopping port 3...done
bye...
 
 
 
 
* Port setup.
 
Network devices using DPDK-compatible driver ============================================
0000:09:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:09:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:81:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:81:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
 
Network devices using kernel driver
===================================
0000:04:00.0 'I350 Gigabit Network Connection' if=em1 drv=igb unused=igb_uio,vfio-pci *Active*
0000:04:00.1 'I350 Gigabit Network Connection' if=em2 drv=igb unused=igb_uio,vfio-pci
0000:04:00.2 'I350 Gigabit Network Connection' if=em3 drv=igb unused=igb_uio,vfio-pci
0000:04:00.3 'I350 Gigabit Network Connection' if=em4 drv=igb unused=igb_uio,vfio-pci
 
Other network devices
=====================
<none>
 
 
* I used 2048 for NUMA node 0, 2048 for NUMA node 1.
 
/proc/meminfo file.
HugePages_Total:    4096
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
 
* Fedora OS version : Fedora release 20 (Heisenbug)
 
* gcc version : gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7).
 
* Intel(R) Xeon(R) CPU E5-2680  10 cores, 64G bytes system memory.
* 2 2-port NIC cards, Intel® 82599ES 10 Gigabit Ethernet 2 port Controller. SFI/SFP+. optical link. Hence there are 4 10 GbE ports.
 
* I attached DPDK setup script in my environment.
 
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.


^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-14  1:29 [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r 최익성
  2015-10-14  1:38 ` Xu, Qian Q
@ 2015-10-14  1:49 ` 최익성
  2015-10-14 13:19   ` De Lara Guarch, Pablo
  1 sibling, 1 reply; 9+ messages in thread
From: 최익성 @ 2015-10-14  1:49 UTC (permalink / raw)
  To: 최익성, dev

 My DPDK setup shell script is as follows.
------------------------------------------------------------------------
 
 
#! /bin/bash
ifconfig -a > ifconfig.out.txt
sudo ifconfig p785p1 down
sudo ifconfig p785p2 down
 
sudo ifconfig p787p1 down
sudo ifconfig p787p2 down
 
setup_target()
{
        option=$1
        export RTE_TARGET=${TARGETS[option]}
 
        compiler=${RTE_TARGET##*-}
        if [ "$compiler" == "icc" ] ; then
                platform=${RTE_TARGET%%-*}
                if [ "$platform" == "x86_64" ] ; then
                        setup_icc intel64
                else
                        setup_icc ia32
                fi
        fi
        if [ "$QUIT" == "0" ] ; then
                make install T=${RTE_TARGET}
        fi
        echo "------------------------------------------------------------------------------"
        echo " RTE_TARGET exported as $RTE_TARGET"
        echo "------------------------------------------------------------------------------"
}
 
load_igb_uio_module()
{
        if [ ! -f $RTE_SDK/$RTE_TARGET/kmod/igb_uio.ko ];then
                echo "## ERROR: Target does not have the DPDK UIO Kernel Module."
                echo "       To fix, please try to rebuild target."
                return
        fi
 
        remove_igb_uio_module
 
        /sbin/lsmod | grep -s uio > /dev/null
        if [ $? -ne 0 ] ; then
                if [ -f /lib/modules/$(uname -r)/kernel/drivers/uio/uio.ko ] ; then
                        echo "Loading uio module"
                        sudo /sbin/modprobe uio
                        sudo /sbin/modprobe vfio-pci
                fi
        fi
 
        # UIO may be compiled into kernel, so it may not be an error if it can't
        # be loaded.
 
        echo "Loading DPDK UIO module"
        sudo /sbin/insmod $RTE_SDK/$RTE_TARGET/kmod/igb_uio.ko
        if [ $? -ne 0 ] ; then
                echo "## ERROR: Could not load kmod/igb_uio.ko."
                quit
        fi
}
#
# Unloads igb_uio.ko.
#
remove_igb_uio_module()
{
        echo "Unloading any existing DPDK UIO module"
        /sbin/lsmod | grep -s igb_uio > /dev/null
        if [ $? -eq 0 ] ; then
                sudo /sbin/rmmod igb_uio
        fi
}
 
create_mnt_huge()
{
        echo "Creating /mnt/huge and mounting as hugetlbfs"
        sudo mkdir -p /mnt/huge
 
        grep -s '/mnt/huge' /proc/mounts > /dev/null
        if [ $? -ne 0 ] ; then
                sudo mount -t hugetlbfs nodev /mnt/huge
        fi
}
set_non_numa_pages()
{
        clear_huge_pages
 
        echo ""
#        echo "  Input the number of 2MB pages"
#        echo "  Example: to have 128MB of hugepages available, enter '64' to"
#        echo "  reserve 64 * 2MB pages"
#        echo -n "Number of pages: "
#        read Pages
#        echo "echo $Pages > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages" > .echo_tmp
 
        echo " Reserve 2048 * 2MB pages"
        echo "echo 2048 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages" > .echo_tmp
 
        echo "Reserving hugepages"
        sudo sh .echo_tmp
        rm -f .echo_tmp
 
        create_mnt_huge
}
 
#
# Creates hugepages on specific NUMA nodes.
#
set_numa_pages()
{
        clear_huge_pages
 
        echo ""
        echo "  Input the number of 2MB pages for each node"
        echo "  Example: to have 128MB of hugepages available per node,"
        echo "  enter '64' to reserve 64 * 2MB pages on each node"
 
        echo > .echo_tmp
        for d in /sys/devices/system/node/node? ; do
                node=$(basename $d)
                echo -n "Number of pages for $node: "
#                read Pages
#                echo "echo $Pages > $d/hugepages/hugepages-2048kB/nr_hugepages" >> .echo_tmp
                echo "echo 2048 > $d/hugepages/hugepages-2048kB/nr_hugepages" >> .echo_tmp
        done
        echo "Reserving hugepages"
        sudo sh .echo_tmp
        rm -f .echo_tmp
 
        create_mnt_huge
}
 
#
# Removes hugepage filesystem.
#
remove_mnt_huge()
{
        echo "Unmounting /mnt/huge and removing directory"
        grep -s '/mnt/huge' /proc/mounts > /dev/null
        if [ $? -eq 0 ] ; then
                sudo umount /mnt/huge
        fi
 
        if [ -d /mnt/huge ] ; then
                sudo rm -R /mnt/huge
        fi
}
#
# Removes all reserved hugepages.
#
clear_huge_pages()
{
        echo > .echo_tmp
        for d in /sys/devices/system/node/node? ; do
                echo "echo 0 > $d/hugepages/hugepages-2048kB/nr_hugepages" >> .echo_tmp
        done
        echo "Removing currently reserved hugepages"
        sudo sh .echo_tmp
        rm -f .echo_tmp
 
        remove_mnt_huge
}
show_nics()
{
        if  /sbin/lsmod  | grep -q igb_uio ; then
                ${RTE_SDK}/tools/dpdk_nic_bind.py --status
        else
                echo "# Please load the 'igb_uio' kernel module before querying or "
                echo "# adjusting NIC device bindings"
        fi
}
bind_nics()
{
        if  /sbin/lsmod  | grep -q igb_uio ; then
                ${RTE_SDK}/tools/dpdk_nic_bind.py --status
                echo ""
#                echo -n "Enter PCI address of device to bind to IGB UIO driver: "
#                read PCI_PATH
                echo "Bind NICs to DPDK"
                sudo ${RTE_SDK}/tools/dpdk_nic_bind.py -b igb_uio 0000:09:00.0 && echo "OK"
                sudo ${RTE_SDK}/tools/dpdk_nic_bind.py -b igb_uio 0000:09:00.1 && echo "OK"
 
                sudo ${RTE_SDK}/tools/dpdk_nic_bind.py -b igb_uio 0000:81:00.0 && echo "OK"
                sudo ${RTE_SDK}/tools/dpdk_nic_bind.py -b igb_uio 0000:81:00.1 && echo "OK"
        else
                echo "# Please load the 'igb_uio' kernel module before querying or "
                echo "# adjusting NIC device bindings"
        fi
}
 
# setup environment &  build DPDK 
 
# export DPDK_DIR=/home/stack/Pktgen-DPDK-master/dpdk
# export RTE_SDK=/home/stack/Pktgen-DPDK-master/dpdk
# export RTE_TARGET=x86_64-pktgen-linuxapp-gcc
export DPDK_DIR=/home/stack/dpdk/
export RTE_SDK=/home/stack/dpdk/
export RTE_TARGET=x86_64-native-linuxapp-gcc
 
# setup environment &  build DPDK 
 
#setup_target
echo "---------------------------------------------------------------------------------------------"
echo "Build DPDK module"
echo "---------------------------------------------------------------------------------------------"
cd $DPDK_DIR
make install T=$RTE_TARGET
 
# Setup linuxapp environment
 
echo "---------------------------------------------------------------------------------------------"
echo "Insert IGB UIO module"
echo "---------------------------------------------------------------------------------------------"
load_igb_uio_module
echo "---------------------------------------------------------------------------------------------"
echo "Setup hugepage mappings for NUMA systems"
echo "---------------------------------------------------------------------------------------------"
# set_non_numa_pages
set_numa_pages
#echo "Display current Ethernet device settings"
#show_nics
echo "---------------------------------------------------------------------------------------------"
echo "Bind current Ethernet device to DPDK"
echo "---------------------------------------------------------------------------------------------"
bind_nics
show_nics
 
 
 
 
-----Original Message-----
From: "최익성"<pnk003@naver.com> 
To: <dev@dpdk.org>; 
Cc: 
Sent: 2015-10-14 (수) 10:29:22
Subject: [dpdk-dev]  I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
 
Dear DPDK experts.
 
Thank you very much for your best great efforts and precious answers.
 
I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug).
 
My problem is that I cannot receive any traffics in test-pmd.
 
There are 2 nics (2 port NIC), I connected port 0 to port 1(loopback), port 2 to port3 (loopback).
 
I attached details of my setup. I also attached my DPDK setup shell script.
 
Did I miss something? or Is there any my mistakes?
 
 
I will really appreciate if you check them and I can be given any advice and answers.
 
 
It is important for me and urgent job.
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.
 
 
* test-pmd log.
 
 
$ sudo ./build/app/testpmd -c 0xF -n 4 -- -i --portmask=0xF --nb-cores=3
 
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 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 1
EAL: Detected lcore 11 as core 1 on socket 1
EAL: Detected lcore 12 as core 2 on socket 1
EAL: Detected lcore 13 as core 3 on socket 1
EAL: Detected lcore 14 as core 4 on socket 1
EAL: Detected lcore 15 as core 8 on socket 1
EAL: Detected lcore 16 as core 9 on socket 1
EAL: Detected lcore 17 as core 10 on socket 1
EAL: Detected lcore 18 as core 11 on socket 1
EAL: Detected lcore 19 as core 12 on socket 1
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 0x1000000 bytes
EAL: Virtual area found at 0x7f85eb000000 (size = 0x1000000)
EAL: Ask a virtual area of 0x3800000 bytes
EAL: Virtual area found at 0x7f85e7600000 (size = 0x3800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f85e7200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f85e6e00000 (size = 0x200000)
EAL: Ask a virtual area of 0xfb400000 bytes
EAL: Virtual area found at 0x7f84eb800000 (size = 0xfb400000)
EAL: Ask a virtual area of 0xffc00000 bytes
EAL: Virtual area found at 0x7f83eba00000 (size = 0xffc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f83eb600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f83eb200000 (size = 0x200000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: Requesting 2048 pages of size 2MB from socket 1
EAL: TSC frequency is ~2793267 KHz
EAL: Master lcore 0 is ready (tid=ee4a0940;cpuset=[0])
EAL: lcore 3 is ready (tid=ea1cf700;cpuset=[3])
EAL: lcore 2 is ready (tid=ecc69700;cpuset=[2])
EAL: lcore 1 is ready (tid=ed46a700;cpuset=[1])
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec000000
EAL:   PCI memory mapped at 0x7f85ec080000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec084000
EAL:   PCI memory mapped at 0x7f85ec104000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 1 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.0 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec108000
EAL:   PCI memory mapped at 0x7f85ec188000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 2 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.1 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f85ec18c000
EAL:   PCI memory mapped at 0x7f85ec20c000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 3 vendorID=0x8086 deviceID=0x10fb
Interactive-mode selected
Configuring Port 0 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f8a5c0 hw_ring=0x7f85e6f8c600 dma_addr=0x6c158c600
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f79cc0 sw_sc_ring=0x7f85e6f79780 hw_ring=0x7f85e6f7a200 dma_addr=0x6c157a200
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 0: 90:E2:BA:8B:BF:C0
Configuring Port 1 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f674c0 hw_ring=0x7f85e6f69500 dma_addr=0x6c1569500
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f56bc0 sw_sc_ring=0x7f85e6f56680 hw_ring=0x7f85e6f57100 dma_addr=0x6c1557100
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 1: 90:E2:BA:8B:BF:C1
Configuring Port 2 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f443c0 hw_ring=0x7f85e6f46400 dma_addr=0x6c1546400
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f33ac0 sw_sc_ring=0x7f85e6f33580 hw_ring=0x7f85e6f34000 dma_addr=0x6c1534000
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 2: 90:E2:BA:8B:B8:CC
Configuring Port 3 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f85e6f212c0 hw_ring=0x7f85e6f23300 dma_addr=0x6c1523300
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f85e6f109c0 sw_sc_ring=0x7f85e6f10480 hw_ring=0x7f85e6f10f00 dma_addr=0x6c1510f00
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 3: 90:E2:BA:8B:B8:CD
Checking link statuses...
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Up - speed 10000 Mbps - full-duplex
Port 2 Link Up - speed 10000 Mbps - full-duplex
Port 3 Link Up - speed 10000 Mbps - full-duplex
Done
 
 
testpmd> show port stats all
  ######################## NIC statistics for port 0  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 5
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 1  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 3
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 2  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 4
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
  ######################## NIC statistics for port 3  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-badcrc:  0          RX-badlen: 0          RX-errors: 3
  RX-nombuf:  0         
  TX-packets: 0          TX-errors: 0          TX-bytes:  0
  ############################################################################
 
 
testpmd> start tx_first  io packet forwarding - CRC stripping disabled - packets/burst=32
  nb forwarding cores=3 - nb forwarding ports=4
  RX queues=1 - RX desc=128 - RX free threshold=32
  RX threshold registers: pthresh=8 hthresh=8 wthresh=0
  TX queues=1 - TX desc=512 - TX free threshold=32
  TX threshold registers: pthresh=32 hthresh=0 wthresh=0
  TX RS bit threshold=32 - TXQ flags=0xf01
 
 
testpmd> 
testpmd> 
testpmd> 
testpmd> stop
 
Telling cores to stop...
Waiting for lcores to finish...
 
  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 5
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 1  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 3
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 2  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 4
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 3  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  RX-badcrc:  0              RX-badlen:  0             RX-error: 3
  RX-nombufs: 0             
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------
 
  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Done.
 
 
testpmd> quitStopping port 0...done
Stopping port 1...done
Stopping port 2...done
Stopping port 3...done
bye...
 
 
 
 
* Port setup.
 
Network devices using DPDK-compatible driver
============================================
0000:09:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:09:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:81:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
0000:81:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,vfio-pci
 
Network devices using kernel driver
===================================
0000:04:00.0 'I350 Gigabit Network Connection' if=em1 drv=igb unused=igb_uio,vfio-pci *Active*
0000:04:00.1 'I350 Gigabit Network Connection' if=em2 drv=igb unused=igb_uio,vfio-pci 
0000:04:00.2 'I350 Gigabit Network Connection' if=em3 drv=igb unused=igb_uio,vfio-pci 
0000:04:00.3 'I350 Gigabit Network Connection' if=em4 drv=igb unused=igb_uio,vfio-pci
 
Other network devices
=====================
<none>
 
 
* I used 2048 for NUMA node 0, 2048 for NUMA node 1.
 
/proc/meminfo file.
HugePages_Total:    4096
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
 
* Fedora OS version : Fedora release 20 (Heisenbug)
 
* gcc version : gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7).
 
* Intel(R) Xeon(R) CPU E5-2680  10 cores, 64G bytes system memory.
* 2 2-port NIC cards, Intel® 82599ES 10 Gigabit Ethernet 2 port Controller. SFI/SFP+. optical link. Hence there are 4 10 GbE ports.
 
* I attached DPDK setup script in my environment.
 
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.


^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-14  1:49 ` 최익성
@ 2015-10-14 13:19   ` De Lara Guarch, Pablo
  2015-10-15  1:01     ` 최익성
  0 siblings, 1 reply; 9+ messages in thread
From: De Lara Guarch, Pablo @ 2015-10-14 13:19 UTC (permalink / raw)
  To: ???, dev

Hi Ick-Sung,

> * Fedora OS version : Fedora release 20 (Heisenbug)
> 
> * gcc version : gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7).
> 
> * Intel(R) Xeon(R) CPU E5-2680  10 cores, 64G bytes system memory.
> * 2 2-port NIC cards, Intel® 82599ES 10 Gigabit Ethernet 2 port Controller.
> SFI/SFP+. optical link. Hence there are 4 10 GbE ports.
> 
> * I attached DPDK setup script in my environment.

What is your kernel version? And also, can you check if you have VT-d enabled?

Thanks,
Pablo
> 
> 
> Thank you very much.
> 
> Sincerely Yours,
> 
> Ick-Sung Choi.


^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-14 13:19   ` De Lara Guarch, Pablo
@ 2015-10-15  1:01     ` 최익성
  2015-10-15  8:02       ` De Lara Guarch, Pablo
  2015-10-15  8:10       ` Mcnamara, John
  0 siblings, 2 replies; 9+ messages in thread
From: 최익성 @ 2015-10-15  1:01 UTC (permalink / raw)
  To: De Lara GuarchPablo, dev

 Dear De Lara Guarch, Pablo.
 
I checked what you mentioned.
 
* Fedora Linux kernel version is as follows.
 
     $ uname -r (print kernel name)
     3.17.7-200.fc20.x86_64
 
     $ uname -a
     Linux sdnlab-k01 3.17.7-200.fc20.x86_64 #1 SMP Wed Dec 17 03:35:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
 
     $ cat /proc/version
     Linux version 3.17.7-200.fc20.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC) ) #1 SMP Wed Dec 17 03:35:33 UTC 2014
 
     $ rpm -q kernel
     kernel-3.11.10-301.fc20.x86_64
     kernel-3.17.7-200.fc20.x86_64
     kernel-3.15.6-200.fc20.x86_64
 
     $ cat /etc/redhat-release
     Fedora release 20 (Heisenbug)
 
 
* Vt-d seems to be enabled. I heard that the result values of 3 or 5 mean the virtualization activated.
 
     $ sudo rdmsr 0x3A
     5
 
And I have strange error during the yum update.
 
 
$ sudo yum update
 
--> Finished Dependency Resolution
--> Running transaction check
---> Package aspell-en.x86_64 50:7.1-6.fc20 will be installed
---> Package kernel-devel.x86_64 0:3.11.10-301.fc20 will be erased
---> Package kernel-modules-extra.x86_64 0:3.11.10-301.fc20 will be erased
---> Package kernel-modules-extra.x86_64 0:3.19.8-100.fc20 will be installed
--> Processing Dependency: kernel-uname-r = 3.19.8-100.fc20.x86_64 for package: kernel-modules-extra-3.19.8-100.fc20.x86_64
--> Finished Dependency Resolution
Error: Package: kernel-modules-extra-3.19.8-100.fc20.x86_64 (updates)
           Requires: kernel-uname-r = 3.19.8-100.fc20.x86_64
           Installed: kernel-3.11.10-301.fc20.x86_64 (@anaconda)
               kernel-uname-r = 3.11.10-301.fc20.x86_64
           Installed: kernel-3.15.6-200.fc20.x86_64 (installed)
               kernel-uname-r = 3.15.6-200.fc20.x86_64
           Installed: kernel-3.17.7-200.fc20.x86_64 (@updates)
               kernel-uname-r = 3.17.7-200.fc20.x86_64
           Available: kernel-debug-3.11.10-301.fc20.x86_64 (fedora)
               kernel-uname-r = 3.11.10-301.fc20.x86_64+debug
           Available: kernel-debug-3.19.8-100.fc20.x86_64 (updates)
               kernel-uname-r = 3.19.8-100.fc20.x86_64+debug
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
 
 
* There are virtual bridge and virtual nic in the Fedora server.
 
$ ifconfig  or $ ifconfig -a
 
virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet ?.?.?.?  netmask 255.255.255.0  broadcast ?.?.?.?
        ether 52:54:00:f2:70:98  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:f2:70:98  txqueuelen 500  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.
 
 
 
-----Original Message-----
From: "De Lara Guarch, Pablo"<pablo.de.lara.guarch@intel.com> 
To: "???"<pnk003@naver.com>; "dev@dpdk.org"<dev@dpdk.org>; 
Cc: 
Sent: 2015-10-14 (수) 22:19:02
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
 
Hi Ick-Sung,



> * Fedora OS version : Fedora release 20 (Heisenbug)

> 

> * gcc version : gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7).

> 

> * Intel(R) Xeon(R) CPU E5-2680  10 cores, 64G bytes system memory.

> * 2 2-port NIC cards, Intel® 82599ES 10 Gigabit Ethernet 2 port Controller.

> SFI/SFP+. optical link. Hence there are 4 10 GbE ports.

> 

> * I attached DPDK setup script in my environment.



What is your kernel version? And also, can you check if you have VT-d enabled?



Thanks,

Pablo

> 

> 

> Thank you very much.

> 

> Sincerely Yours,

> 

> Ick-Sung Choi.




^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-15  1:01     ` 최익성
@ 2015-10-15  8:02       ` De Lara Guarch, Pablo
  2015-10-15  8:10       ` Mcnamara, John
  1 sibling, 0 replies; 9+ messages in thread
From: De Lara Guarch, Pablo @ 2015-10-15  8:02 UTC (permalink / raw)
  To: ???, dev

Hi,

From: 최익성 [mailto:pnk003@naver.com]
Sent: Thursday, October 15, 2015 2:02 AM
To: De Lara Guarch, Pablo; dev@dpdk.org
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r


Dear De Lara Guarch, Pablo.



I checked what you mentioned.



* Fedora Linux kernel version is as follows.



     $ uname -r (print kernel name)

     3.17.7-200.fc20.x86_64



     $ uname -a

     Linux sdnlab-k01 3.17.7-200.fc20.x86_64 #1 SMP Wed Dec 17 03:35:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux



     $ cat /proc/version

     Linux version 3.17.7-200.fc20.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org<mailto:mockbuild@bkernel01.phx2.fedoraproject.org>) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC) ) #1 SMP Wed Dec 17 03:35:33 UTC 2014



     $ rpm -q kernel

     kernel-3.11.10-301.fc20.x86_64

     kernel-3.17.7-200.fc20.x86_64

     kernel-3.15.6-200.fc20.x86_64



     $ cat /etc/redhat-release

     Fedora release 20 (Heisenbug)





* Vt-d seems to be enabled. I heard that the result values of 3 or 5 mean the virtualization activated.



     $ sudo rdmsr 0x3A

     5



If VT-d is enabled, and you are running on the host, you need to use “intel_iommu=on iommu=pt” in the kernel parameters.

Anyway, there is a known issue with kernels between 3.15 and 3.17, with VT-d: take a look at the bug 6.25 here:

http://dpdk.readthedocs.org/en/v2.1.0/rel_notes/known_issues.html



I suggest you  to disable VT-d and see if you problem goes away, and if so,



update your kernel and include the line above if you need VT-d enabled for any reason.



And I have strange error during the yum update.





$ sudo yum update



--> Finished Dependency Resolution

--> Running transaction check

---> Package aspell-en.x86_64 50:7.1-6.fc20 will be installed

---> Package kernel-devel.x86_64 0:3.11.10-301.fc20 will be erased

---> Package kernel-modules-extra.x86_64 0:3.11.10-301.fc20 will be erased

---> Package kernel-modules-extra.x86_64 0:3.19.8-100.fc20 will be installed

--> Processing Dependency: kernel-uname-r = 3.19.8-100.fc20.x86_64 for package: kernel-modules-extra-3.19.8-100.fc20.x86_64

--> Finished Dependency Resolution

Error: Package: kernel-modules-extra-3.19.8-100.fc20.x86_64 (updates)

           Requires: kernel-uname-r = 3.19.8-100.fc20.x86_64

           Installed: kernel-3.11.10-301.fc20.x86_64 (@anaconda)

               kernel-uname-r = 3.11.10-301.fc20.x86_64

           Installed: kernel-3.15.6-200.fc20.x86_64 (installed)

               kernel-uname-r = 3.15.6-200.fc20.x86_64

           Installed: kernel-3.17.7-200.fc20.x86_64 (@updates)

               kernel-uname-r = 3.17.7-200.fc20.x86_64

           Available: kernel-debug-3.11.10-301.fc20.x86_64 (fedora)

               kernel-uname-r = 3.11.10-301.fc20.x86_64+debug

           Available: kernel-debug-3.19.8-100.fc20.x86_64 (updates)

               kernel-uname-r = 3.19.8-100.fc20.x86_64+debug

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest





* There are virtual bridge and virtual nic in the Fedora server.



$ ifconfig  or $ ifconfig -a



virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        inet ?.?.?.?  netmask 255.255.255.0  broadcast ?.?.?.?

        ether 52:54:00:f2:70:98  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500

        ether 52:54:00:f2:70:98  txqueuelen 500  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0





Thank you very much.



Sincerely Yours,



Ick-Sung Choi.







-----Original Message-----
From: "De Lara Guarch, Pablo"<pablo.de.lara.guarch@intel.com<mailto:pablo.de.lara.guarch@intel.com>>
To: "???"<pnk003@naver.com<mailto:pnk003@naver.com>>; "dev@dpdk.org<mailto:dev@dpdk.org>"<dev@dpdk.org<mailto:dev@dpdk.org>>;
Cc:
Sent: 2015-10-14 (수) 22:19:02
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r

Hi Ick-Sung,

> * Fedora OS version : Fedora release 20 (Heisenbug)
>
> * gcc version : gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7).
>
> * Intel(R) Xeon(R) CPU E5-2680 10 cores, 64G bytes system memory.
> * 2 2-port NIC cards, Intel® 82599ES 10 Gigabit Ethernet 2 port Controller.
> SFI/SFP+. optical link. Hence there are 4 10 GbE ports.
>
> * I attached DPDK setup script in my environment.

What is your kernel version? And also, can you check if you have VT-d enabled?

Thanks,
Pablo
>
>
> Thank you very much.
>
> Sincerely Yours,
>
> Ick-Sung Choi.
[http://mail.naver.com/readReceipt/notify/?img=b9nqKAIOWNgqpoFvaxmsa6MwMrtrpAvwFrE9pxbdMquZMobqpovmpz3gMX%2B0MoUd74lR74lcWNFlbX30WLloWrdQaXICM4wT743074wCb4u5pXkCb4Fctz05%2Bzkn74FTWt%3D%3D.gif]



^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-15  1:01     ` 최익성
  2015-10-15  8:02       ` De Lara Guarch, Pablo
@ 2015-10-15  8:10       ` Mcnamara, John
  2015-10-15 23:46         ` 최익성
  2015-10-19 14:48         ` 최익성
  1 sibling, 2 replies; 9+ messages in thread
From: Mcnamara, John @ 2015-10-15  8:10 UTC (permalink / raw)
  To: ???, De Lara Guarch, Pablo, dev

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ???
> Sent: Thursday, October 15, 2015 2:02 AM
> To: De Lara Guarch, Pablo; dev@dpdk.org
> Subject: Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in
> Fedora OS release 20 (Heisenbug). I cannot r
>
> I checked what you mentioned.
> 
> * Fedora Linux kernel version is as follows.
> 
>      $ uname -r (print kernel name)
>      3.17.7-200.fc20.x86_64

Hi,

This may be a known issue. See:


http://dpdk.org/doc/guides/rel_notes/known_issues.html#devices-bound-to-igb-uio-with-vt-d-enabled-do-not-work-on-linux-kernel-3-15-3-17


"Devices bound to igb_uio with VT-d enabled do not work on Linux kernel 3.15-3.17

Description:
    When VT-d is enabled (iommu=pt intel_iommu=on), devices are 1:1 mapped. In the Linux kernel unbinding devices from drivers removes that mapping which result in IOMMU errors. Introduced in Linux kernel 3.15 commit, solved in Linux kernel 3.18 commit."

John

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-15  8:10       ` Mcnamara, John
@ 2015-10-15 23:46         ` 최익성
  2015-10-19 14:48         ` 최익성
  1 sibling, 0 replies; 9+ messages in thread
From: 최익성 @ 2015-10-15 23:46 UTC (permalink / raw)
  To: McnamaraJohn, De Lara GuarchPablo, dev

  
Dear John Manamara and DPDK experts.
 
Thank you very much for your precious advice and answer.
 
I will try to upgrade the OS.
 
I really appreciate to you for your excellent work and great contributions.
 
Sincerely Yours,
 
Ick-Sung Choi.

-----Original Message-----
From: "Mcnamara, John"&lt;john.mcnamara@intel.com&gt; 
To: "???"&lt;pnk003@naver.com&gt;; "De Lara Guarch, Pablo"&lt;pablo.de.lara.guarch@intel.com&gt;; "dev@dpdk.org"&lt;dev@dpdk.org&gt;; 
Cc: 
Sent: 2015-10-15 (목) 17:10:48
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
 
&gt; -----Original Message-----

&gt; From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ???

&gt; Sent: Thursday, October 15, 2015 2:02 AM

&gt; To: De Lara Guarch, Pablo; dev@dpdk.org

&gt; Subject: Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in

&gt; Fedora OS release 20 (Heisenbug). I cannot r

&gt;

&gt; I checked what you mentioned.

&gt; 

&gt; * Fedora Linux kernel version is as follows.

&gt; 

&gt;      $ uname -r (print kernel name)

&gt;      3.17.7-200.fc20.x86_64



Hi,



This may be a known issue. See:





http://dpdk.org/doc/guides/rel_notes/known_issues.html#devices-bound-to-igb-uio-with-vt-d-enabled-do-not-work-on-linux-kernel-3-15-3-17





"Devices bound to igb_uio with VT-d enabled do not work on Linux kernel 3.15-3.17



Description:

    When VT-d is enabled (iommu=pt intel_iommu=on), devices are 1:1 mapped. In the Linux kernel unbinding devices from drivers removes that mapping which result in IOMMU errors. Introduced in Linux kernel 3.15 commit, solved in Linux kernel 3.18 commit."



John


^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
  2015-10-15  8:10       ` Mcnamara, John
  2015-10-15 23:46         ` 최익성
@ 2015-10-19 14:48         ` 최익성
  1 sibling, 0 replies; 9+ messages in thread
From: 최익성 @ 2015-10-19 14:48 UTC (permalink / raw)
  To: McnamaraJohn, De Lara GuarchPablo, dev

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 14256 bytes --]

 Dear DPDK experts.
 
Thank you very much for your best great efforts and precious answers.
 
As you suggested, I reinstalled newer version of Fedora 22.
 
I succeeded to communicate test-pmd in Fedora 22 (linux kernel version 4.2.3-200.fc22.x86_64, DPDK 2.1.0).
 
The steps are as follows.
 
 
sudo yum install gcc
sudo yum install kernel-devel
sudo yum install libpcap-devel 
 
And then I patched the source codes as in  http://dpdk.org/dev/patchwork/patch/6800/   Patchwork [dpdk-dev] kni: fix igb build with kernel 4.2.
 
And then, I followed the quick start instructions from http://dpdk.org/doc/quick-start .
 
The test-pmd example seems to work.
 
Thank you very much.
 
 
 
I have another problem.
 
As in the following test-pmd log scripts, most of received packets are RX-error.
 
The same errors are occurred in the Ubuntu OS computer (Ubuntu 14.04.1 LTS, kernel version : 3.13.0-34-generic, DPDK 2.1.0).  
 
If you have any advices or answers for the above problem, I will really appreciate.
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.
 
 
----------------------------------------------------------------------
test-pmd scripts:
 
 
$ sudo ./build/app/testpmd -c 0xFF -n 4 -- -i --portmask=0x3 --nb-cores=2
 
 
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 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 1
EAL: Detected lcore 11 as core 1 on socket 1
EAL: Detected lcore 12 as core 2 on socket 1
EAL: Detected lcore 13 as core 3 on socket 1
EAL: Detected lcore 14 as core 4 on socket 1
EAL: Detected lcore 15 as core 8 on socket 1
EAL: Detected lcore 16 as core 9 on socket 1
EAL: Detected lcore 17 as core 10 on socket 1
EAL: Detected lcore 18 as core 11 on socket 1
EAL: Detected lcore 19 as core 12 on socket 1
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 20 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x54000000 bytes
EAL: Virtual area found at 0x7f678a000000 (size = 0x54000000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f6789800000 (size = 0x600000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f6789000000 (size = 0x600000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f6788600000 (size = 0x800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f6788200000 (size = 0x200000)
EAL: Ask a virtual area of 0x9c400000 bytes
EAL: Virtual area found at 0x7f66ebc00000 (size = 0x9c400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66eb800000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66eb400000 (size = 0x200000)
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7f66e9600000 (size = 0x1c00000)
EAL: Ask a virtual area of 0x1200000 bytes
EAL: Virtual area found at 0x7f66e8200000 (size = 0x1200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f66e7c00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f66e7600000 (size = 0x400000)
EAL: Ask a virtual area of 0x3800000 bytes
EAL: Virtual area found at 0x7f66e3c00000 (size = 0x3800000)
EAL: Ask a virtual area of 0x5000000 bytes
EAL: Virtual area found at 0x7f66dea00000 (size = 0x5000000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66de600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66de200000 (size = 0x200000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f66dd400000 (size = 0xc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66dd000000 (size = 0x200000)
EAL: Ask a virtual area of 0xa00000 bytes
EAL: Virtual area found at 0x7f66dc400000 (size = 0xa00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66dc000000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f66dba00000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66db600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66db200000 (size = 0x200000)
EAL: Ask a virtual area of 0xf4000000 bytes
EAL: Virtual area found at 0x7f65e7000000 (size = 0xf4000000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65e6a00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65e6400000 (size = 0x400000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f65e5c00000 (size = 0x600000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f65e4e00000 (size = 0xc00000)
EAL: Ask a virtual area of 0x3a00000 bytes
EAL: Virtual area found at 0x7f65e1200000 (size = 0x3a00000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f65e0a00000 (size = 0x600000)
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7f65dec00000 (size = 0x1c00000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65de600000 (size = 0x400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f65dd800000 (size = 0xc00000)
EAL: Ask a virtual area of 0xe00000 bytes
EAL: Virtual area found at 0x7f65dc800000 (size = 0xe00000)
EAL: Ask a virtual area of 0x1400000 bytes
EAL: Virtual area found at 0x7f65db200000 (size = 0x1400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f65da400000 (size = 0xc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f65da000000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65d9a00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65d9400000 (size = 0x400000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: Requesting 2048 pages of size 2MB from socket 1
EAL: TSC frequency is ~2793270 KHz
EAL: Master lcore 0 is ready (tid=e0bfb8c0;cpuset=[0])
EAL: lcore 7 is ready (tid=d63cb700;cpuset=[7])
EAL: lcore 4 is ready (tid=d7bce700;cpuset=[4])
EAL: lcore 6 is ready (tid=d6bcc700;cpuset=[6])
EAL: lcore 2 is ready (tid=decf8700;cpuset=[2])
EAL: lcore 3 is ready (tid=d83cf700;cpuset=[3])
EAL: lcore 5 is ready (tid=d73cd700;cpuset=[5])
EAL: lcore 1 is ready (tid=df4f9700;cpuset=[1])
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de000000
EAL:   PCI memory mapped at 0x7f67de080000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de084000
EAL:   PCI memory mapped at 0x7f67de104000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 1 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.0 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de108000
EAL:   PCI memory mapped at 0x7f67de188000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 2 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.1 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de18c000
EAL:   PCI memory mapped at 0x7f67de20c000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 3 vendorID=0x8086 deviceID=0x10fb
Interactive-mode selected
previous number of forwarding ports 4 - changed to number of configured ports 2
Configuring Port 0 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77ed9c0 hw_ring=0x7f66e77efa00 dma_addr=0x7effefa00
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e77dd0c0 sw_sc_ring=0x7f66e77dcb80 hw_ring=0x7f66e77dd600 dma_addr=0x7effdd600
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 0: 90:E2:BA:8B:BF:C0
Configuring Port 1 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77ca8c0 hw_ring=0x7f66e77cc900 dma_addr=0x7effcc900
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e77b9fc0 sw_sc_ring=0x7f66e77b9a80 hw_ring=0x7f66e77ba500 dma_addr=0x7effba500
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 1: 90:E2:BA:8B:BF:C1
Configuring Port 2 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77a77c0 hw_ring=0x7f66e77a9800 dma_addr=0x7effa9800
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e7796ec0 sw_sc_ring=0x7f66e7796980 hw_ring=0x7f66e7797400 dma_addr=0x7eff97400
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 2: 90:E2:BA:8B:B8:CC
Configuring Port 3 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77846c0 hw_ring=0x7f66e7786700 dma_addr=0x7eff86700
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e7773dc0 sw_sc_ring=0x7f66e7773880 hw_ring=0x7f66e7774300 dma_addr=0x7eff74300
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 3: 90:E2:BA:8B:B8:CD
Checking link statuses...
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Up - speed 10000 Mbps - full-duplex
Port 2 Link Down
Port 3 Link Down
Done
testpmd&gt; start tx_first  io packet forwarding - CRC stripping disabled - packets/burst=32
  nb forwarding cores=2 - nb forwarding ports=2
  RX queues=1 - RX desc=128 - RX free threshold=32
  RX threshold registers: pthresh=8 hthresh=8 wthresh=0
  TX queues=1 - TX desc=512 - TX free threshold=32
  TX threshold registers: pthresh=32 hthresh=0 wthresh=0
  TX RS bit threshold=32 - TXQ flags=0xf01
testpmd&gt; testpmd&gt; testpmd&gt; stopTelling cores to stop...
Waiting for lcores to finish...
 
  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 60646433       RX-dropped: 0             RX-total: 60646433
  RX-badcrc:  0              RX-badlen:  0             RX-error: 60646438
  RX-nombufs: 0             
  TX-packets: 60633255       TX-dropped: 0             TX-total: 60633255
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 1  ----------------------
  RX-packets: 60633255       RX-dropped: 0             RX-total: 60633255
  RX-badcrc:  0              RX-badlen:  0             RX-error: 60633258
  RX-nombufs: 0             
  TX-packets: 60646433       TX-dropped: 0             TX-total: 60646433
  ----------------------------------------------------------------------------
 
  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 121279688      RX-dropped: 0             RX-total: 121279688
  TX-packets: 121279688      TX-dropped: 0             TX-total: 121279688
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Done.
testpmd&gt; testpmd&gt; quitStopping port 0...done
Stopping port 1...done
Stopping port 2...done
Stopping port 3...done
bye...
 
 
 
 
 
 
 
-----Original Message-----
From: "Mcnamara, John"&lt;john.mcnamara@intel.com&gt; 
To: "???"&lt;pnk003@naver.com&gt;; "De Lara Guarch, Pablo"&lt;pablo.de.lara.guarch@intel.com&gt;; "dev@dpdk.org"&lt;dev@dpdk.org&gt;; 
Cc: 
Sent: 2015-10-15 (목) 17:10:48
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
 
&gt; -----Original Message-----

&gt; From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ???

&gt; Sent: Thursday, October 15, 2015 2:02 AM

&gt; To: De Lara Guarch, Pablo; dev@dpdk.org

&gt; Subject: Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in

&gt; Fedora OS release 20 (Heisenbug). I cannot r

&gt;

&gt; I checked what you mentioned.

&gt; 

&gt; * Fedora Linux kernel version is as follows.

&gt; 

&gt;      $ uname -r (print kernel name)

&gt;      3.17.7-200.fc20.x86_64



Hi,



This may be a known issue. See:





http://dpdk.org/doc/guides/rel_notes/known_issues.html#devices-bound-to-igb-uio-with-vt-d-enabled-do-not-work-on-linux-kernel-3-15-3-17





"Devices bound to igb_uio with VT-d enabled do not work on Linux kernel 3.15-3.17



Description:

    When VT-d is enabled (iommu=pt intel_iommu=on), devices are 1:1 mapped. In the Linux kernel unbinding devices from drivers removes that mapping which result in IOMMU errors. Introduced in Linux kernel 3.15 commit, solved in Linux kernel 3.18 commit."



John

\x16º&¶\x1a&jɨž6¥¢~°Šw\¢c(œç-×Ý{ÓMûÛMyEën®sÚ¶^[a¢f¬š‰ãjZ'ë\b§uÊ&Eç\x1eŠ÷~º&™¨¥•½\x1f׿ ¢ˆ%yÊ&™¨¥•½\x1f׿ ¢ˆ%yÊ&ÛO|çm{׿^[ÉÚ]’Šà>‹-~,pŠØDHÄω޽÷nAëgè­×¯v—d¢¸\f¢}}9ËvÓ^uïM7ïí6Ó@„I4^qè¯yÖò•¶ðo|"¶\x14ŒLøÁ½ì£Î<ómùÖVÛÕú+uëÝ¥Ù(®\x03(Ÿ_Nrݴם<ÓMûÓ½4<4×\x1aŠ •àÊ Ä¢‚v­º·¯

^ permalink raw reply	[flat|nested] 9+ messages in thread
end of thread, other threads:[~2015-10-19 14:48 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-14  1:29 [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r 최익성
2015-10-14  1:38 ` Xu, Qian Q
2015-10-14  1:49 ` 최익성
2015-10-14 13:19   ` De Lara Guarch, Pablo
2015-10-15  1:01     ` 최익성
2015-10-15  8:02       ` De Lara Guarch, Pablo
2015-10-15  8:10       ` Mcnamara, John
2015-10-15 23:46         ` 최익성
2015-10-19 14:48         ` 최익성

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).