[dpdk-dev] rte_eth_dev_configure

[dpdk-dev] rte_eth_dev_configure

[sothy shan]

Hello!

I am trying to use DPDK  ovs (development branch) with DPDK1.7.

There is an error when running ovs_dpdk command.

Error is

PANIC in ovdk_vport_phy_port_init.
Cannot initi NIC port 0 (-22).

Based on my search within code, rte_eth_dev_configure gives an error with
code -22.

My question is that how to debug or print the PMD_DEBUG_TRACE into file or
terminal when running ovs-dpdk?

Second, any clue why rte_eth_dev_configure give an error with code -22?

Thanks for your help.

Best regards
Sothy

Re: [dpdk-dev] rte_eth_dev_configure

[Thomas Monjalon]

Hello,

2014-07-24 14:34, sothy shan:
> I am trying to use DPDK  ovs (development branch) with DPDK1.7.

Could you try with testpmd?

> Cannot initi NIC port 0 (-22).
> 
> Based on my search within code, rte_eth_dev_configure gives an error with
> code -22.

Which driver are you using?

> My question is that how to debug or print the PMD_DEBUG_TRACE into file or
> terminal when running ovs-dpdk?

The default is to print on stdout.

> Second, any clue why rte_eth_dev_configure give an error with code -22?

It depends of your driver.
Example: #define IXGBE_ERR_NO_SAN_ADDR_PTR -22

-- 
Thomas

Re: [dpdk-dev] rte_eth_dev_configure

[Thomas Monjalon]

2014-07-24 14:44, Thomas Monjalon:
> 2014-07-24 14:34, sothy shan:
> > Second, any clue why rte_eth_dev_configure give an error with code -22?
> 
> It depends of your driver.
> Example: #define IXGBE_ERR_NO_SAN_ADDR_PTR -22

It's more probably -EINVAL without driver dependency.
It means there is a mistake in your configuration.
PMD_DEBUG_TRACE will help you.

-- 
Thomas

Re: [dpdk-dev] rte_eth_dev_configure

[sothy shan]

I have problem when I try dpdk ovs with DPDK 1.7. DPDK 1.7 alone working
well.

Drive I installed is compiled with T=x86_64-ivshmem-linuxapp-gcc.

I am not sure when I using DPDK ovs, how to debug at DPDK 1.7.0 code. I
guess I need to enable to print PMD_DEBUG_TRACE message. At this point,
DPDK ovs message is only printed.

I too suspect it is problem with port_conf message. Not sure. First I need
to know how to use PMD_DEBUG_TRACE with DPDK_ovs.

You understand my question?

Thanks again



On Thu, Jul 24, 2014 at 2:51 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:

> 2014-07-24 14:44, Thomas Monjalon:
> > 2014-07-24 14:34, sothy shan:
> > > Second, any clue why rte_eth_dev_configure give an error with code -22?
> >
> > It depends of your driver.
> > Example: #define IXGBE_ERR_NO_SAN_ADDR_PTR -22
>
> It's more probably -EINVAL without driver dependency.
> It means there is a mistake in your configuration.
> PMD_DEBUG_TRACE will help you.
>
> --
> Thomas
>

Re: [dpdk-dev] rte_eth_dev_configure

[Thomas Monjalon]

2014-07-24 15:00, sothy shan:
> I have problem when I try dpdk ovs with DPDK 1.7. DPDK 1.7 alone working
> well.
[...]
> I am not sure when I using DPDK ovs, how to debug at DPDK 1.7.0 code. I
> guess I need to enable to print PMD_DEBUG_TRACE message. At this point,
> DPDK ovs message is only printed.

You should enable CONFIG_RTE_LIBRTE_ETHDEV_DEBUG before compiling.

> I too suspect it is problem with port_conf message. Not sure. First I need
> to know how to use PMD_DEBUG_TRACE with DPDK_ovs.
> 
> You understand my question?

Yes I understand that you should enable debugging and ask for help on the
right mailling list.
If DPDK alone works well, we cannot do anything for you.

-- 
Thomas

Re: [dpdk-dev] rte_eth_dev_configure

[sothy shan]

Thanks and it is working and help me a lot.

On Thu, Jul 24, 2014 at 3:05 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:

> 2014-07-24 15:00, sothy shan:
> > I have problem when I try dpdk ovs with DPDK 1.7. DPDK 1.7 alone working
> > well.
> [...]
> > I am not sure when I using DPDK ovs, how to debug at DPDK 1.7.0 code. I
> > guess I need to enable to print PMD_DEBUG_TRACE message. At this point,
> > DPDK ovs message is only printed.
>
> You should enable CONFIG_RTE_LIBRTE_ETHDEV_DEBUG before compiling.
>
> > I too suspect it is problem with port_conf message. Not sure. First I
> need
> > to know how to use PMD_DEBUG_TRACE with DPDK_ovs.
> >
> > You understand my question?
>
> Yes I understand that you should enable debugging and ask for help on the
> right mailling list.
> If DPDK alone works well, we cannot do anything for you.
>
> --
> Thomas
>