* [dpdk-dev] Problem with using VF: Initialization Failure: -15
@ 2018-04-11 12:01 Weglicki, MichalX
2018-04-11 14:12 ` Stephen Hemminger
2018-04-13 7:03 ` Rosen, Rami
0 siblings, 2 replies; 4+ messages in thread
From: Weglicki, MichalX @ 2018-04-11 12:01 UTC (permalink / raw)
To: dev
Hello,
I'm trying to test very simple scenario, creating two VFs and testing it with test-pmd. Unfortunately I can't make it to work
DPDK Version: v17.11 (I've checked also 18.02)
NIC: Niantic 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
Kernel: 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Steps:
Creating two VFs. Binding each VF to a driver (I also tried vfio_pci with same results):
../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.0
../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.1
./testpmd -c 0x3 -n 4 --socket-mem 512 -- --burst=64 -i --txqflags=0xf00 --disable-hw-vlan
EAL: Detected 56 lcore(s)
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:03:00.3 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:05:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:05:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:81:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:81:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:81:10.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10ed net_ixgbe_vf
PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
EAL: Requested device 0000:81:10.0 cannot be used
EAL: PCI device 0000:81:10.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10ed net_ixgbe_vf
PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
EAL: Requested device 0000:81:10.1 cannot be used
EAL: PCI device 0000:83:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:83:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: No probed ethernet devices
Interactive-mode selected
I've investigated the issue, and the problem is with:
diag = hw->mac.ops.reset_hw(hw);
which calls:
e1000_reset_hw_vf
and it calls:
e1000_read_posted_mbx
Which returns: E1000_ERR_MBX (-15)
Is this common issue, or some configuration problem?
Thank you all in advance.
Br,
Michal.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Problem with using VF: Initialization Failure: -15
2018-04-11 12:01 [dpdk-dev] Problem with using VF: Initialization Failure: -15 Weglicki, MichalX
@ 2018-04-11 14:12 ` Stephen Hemminger
2018-04-13 7:03 ` Rosen, Rami
1 sibling, 0 replies; 4+ messages in thread
From: Stephen Hemminger @ 2018-04-11 14:12 UTC (permalink / raw)
To: Weglicki, MichalX; +Cc: dev
On Wed, 11 Apr 2018 12:01:09 +0000
"Weglicki, MichalX" <michalx.weglicki@intel.com> wrote:
> Hello,
>
> I'm trying to test very simple scenario, creating two VFs and testing it with test-pmd. Unfortunately I can't make it to work
> DPDK Version: v17.11 (I've checked also 18.02)
> NIC: Niantic 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
> Kernel: 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> Steps:
> Creating two VFs. Binding each VF to a driver (I also tried vfio_pci with same results):
> ../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.0
> ../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.1
>
> ./testpmd -c 0x3 -n 4 --socket-mem 512 -- --burst=64 -i --txqflags=0xf00 --disable-hw-vlan
> EAL: Detected 56 lcore(s)
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:03:00.3 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:05:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:05:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:10.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10ed net_ixgbe_vf
> PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> EAL: Requested device 0000:81:10.0 cannot be used
> EAL: PCI device 0000:81:10.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10ed net_ixgbe_vf
> PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> EAL: Requested device 0000:81:10.1 cannot be used
> EAL: PCI device 0000:83:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:83:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: No probed ethernet devices
> Interactive-mode selected
>
> I've investigated the issue, and the problem is with:
> diag = hw->mac.ops.reset_hw(hw);
> which calls:
> e1000_reset_hw_vf
> and it calls:
> e1000_read_posted_mbx
> Which returns: E1000_ERR_MBX (-15)
>
> Is this common issue, or some configuration problem?
>
> Thank you all in advance.
>
> Br,
> Michal.
What host? It could be that ixgbevf communication (over mailbox) is not supported
by the older PF driver on the host.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Problem with using VF: Initialization Failure: -15
2018-04-11 12:01 [dpdk-dev] Problem with using VF: Initialization Failure: -15 Weglicki, MichalX
2018-04-11 14:12 ` Stephen Hemminger
@ 2018-04-13 7:03 ` Rosen, Rami
2018-04-16 6:35 ` Weglicki, MichalX
1 sibling, 1 reply; 4+ messages in thread
From: Rosen, Rami @ 2018-04-13 7:03 UTC (permalink / raw)
To: Weglicki, MichalX, dev
Hi, Michal,
First, I believe that such questions suit better to the dpdk-users mailing list.
>I've investigated the issue, and the problem is with:
>diag = hw->mac.ops.reset_hw(hw);
>which calls:
>e1000_reset_hw_vf
>and it calls:
>e1000_read_posted_mbx
>Which returns: E1000_ERR_MBX (-15)
Are you sure about it ? the path that you present in your investigation
is from drivers/net/e1000, whereas the test that you ran is on top of ixgbe,
which has a different PMD driver (drivers/net/ixgbe). The setup that you describe does not use e1000 device at all, according to my understanding.
Regards,
Rami Rosen
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Weglicki, MichalX
Sent: Wednesday, April 11, 2018 15:01
To: dev@dpdk.org
Subject: [dpdk-dev] Problem with using VF: Initialization Failure: -15
Hello,
I'm trying to test very simple scenario, creating two VFs and testing it with test-pmd. Unfortunately I can't make it to work DPDK Version: v17.11 (I've checked also 18.02)
NIC: Niantic 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
Kernel: 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Steps:
Creating two VFs. Binding each VF to a driver (I also tried vfio_pci with same results):
../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.0 ../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.1
./testpmd -c 0x3 -n 4 --socket-mem 512 -- --burst=64 -i --txqflags=0xf00 --disable-hw-vlan
EAL: Detected 56 lcore(s)
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:03:00.3 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:05:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:05:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:81:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:81:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:81:10.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10ed net_ixgbe_vf
PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
EAL: Requested device 0000:81:10.0 cannot be used
EAL: PCI device 0000:81:10.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10ed net_ixgbe_vf
PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
EAL: Requested device 0000:81:10.1 cannot be used
EAL: PCI device 0000:83:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:83:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: No probed ethernet devices
Interactive-mode selected
I've investigated the issue, and the problem is with:
diag = hw->mac.ops.reset_hw(hw);
which calls:
e1000_reset_hw_vf
and it calls:
e1000_read_posted_mbx
Which returns: E1000_ERR_MBX (-15)
Is this common issue, or some configuration problem?
Thank you all in advance.
Br,
Michal.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Problem with using VF: Initialization Failure: -15
2018-04-13 7:03 ` Rosen, Rami
@ 2018-04-16 6:35 ` Weglicki, MichalX
0 siblings, 0 replies; 4+ messages in thread
From: Weglicki, MichalX @ 2018-04-16 6:35 UTC (permalink / raw)
To: Rosen, Rami, dev
Hello,
Yes, sorry, the code flow I've presented was taken from investigation of vfio_pci, but I'm not sure which hardware exactly (I've tested also some other HWs). If it still doesn't make sense, maybe those are wrong assumptions.
Should I resent this question to user@dpdk.org ? I don't want to cause confusion now when it's here already.
Br,
Michal.
> -----Original Message-----
> From: Rosen, Rami
> Sent: Friday, April 13, 2018 9:03 AM
> To: Weglicki, MichalX <michalx.weglicki@intel.com>; dev@dpdk.org
> Subject: RE: Problem with using VF: Initialization Failure: -15
>
> Hi, Michal,
>
> First, I believe that such questions suit better to the dpdk-users mailing list.
>
> >I've investigated the issue, and the problem is with:
> >diag = hw->mac.ops.reset_hw(hw);
> >which calls:
> >e1000_reset_hw_vf
> >and it calls:
> >e1000_read_posted_mbx
> >Which returns: E1000_ERR_MBX (-15)
>
> Are you sure about it ? the path that you present in your investigation
> is from drivers/net/e1000, whereas the test that you ran is on top of ixgbe,
> which has a different PMD driver (drivers/net/ixgbe). The setup that you describe does not use e1000 device at all, according to my
> understanding.
>
> Regards,
> Rami Rosen
>
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Weglicki, MichalX
> Sent: Wednesday, April 11, 2018 15:01
> To: dev@dpdk.org
> Subject: [dpdk-dev] Problem with using VF: Initialization Failure: -15
>
> Hello,
>
> I'm trying to test very simple scenario, creating two VFs and testing it with test-pmd. Unfortunately I can't make it to work DPDK
> Version: v17.11 (I've checked also 18.02)
> NIC: Niantic 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
> Kernel: 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> Steps:
> Creating two VFs. Binding each VF to a driver (I also tried vfio_pci with same results):
> ../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.0 ../dpdk/usertools/dpdk-devbind.py --bind=igb_uio 0000:81:10.1
>
> ./testpmd -c 0x3 -n 4 --socket-mem 512 -- --burst=64 -i --txqflags=0xf00 --disable-hw-vlan
> EAL: Detected 56 lcore(s)
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:03:00.3 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:05:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:05:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:81:10.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10ed net_ixgbe_vf
> PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> EAL: Requested device 0000:81:10.0 cannot be used
> EAL: PCI device 0000:81:10.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10ed net_ixgbe_vf
> PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> EAL: Requested device 0000:81:10.1 cannot be used
> EAL: PCI device 0000:83:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:83:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10fb net_ixgbe
> EAL: No probed ethernet devices
> Interactive-mode selected
>
> I've investigated the issue, and the problem is with:
> diag = hw->mac.ops.reset_hw(hw);
> which calls:
> e1000_reset_hw_vf
> and it calls:
> e1000_read_posted_mbx
> Which returns: E1000_ERR_MBX (-15)
>
> Is this common issue, or some configuration problem?
>
> Thank you all in advance.
>
> Br,
> Michal.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-04-16 6:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-11 12:01 [dpdk-dev] Problem with using VF: Initialization Failure: -15 Weglicki, MichalX
2018-04-11 14:12 ` Stephen Hemminger
2018-04-13 7:03 ` Rosen, Rami
2018-04-16 6:35 ` Weglicki, MichalX
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).