[dpdk-dev] Queries on DPDK working with XL710 intel NIC
Roberts, Lee A.
lee.roberts at hp.com
Fri Mar 20 16:30:35 CET 2015
Nissim,
Recent HP ProLiant servers use RMRRs (see https://www.kernel.org/doc/Documentation/Intel-IOMMU.txt)
to communicate management information. Use of these RMRRs conflicts with IOMMU usage.
On ProLiant Gen8 servers, you have a couple options:
1) If you are doing bare-metal testing and don't require the IOMMU, turn it off.
Some kernels have "intel_iommu=on" set by default. You should be able to use
"intel_iommu=off" if your kernel enables IOMMU by default.
2) If your application requires the IOMMU, there are BIOS parameters that can be
configured to eliminate the RMRRs on a slot-by-slot basis. (I will send instructions
for this separately, since it is not a DPDK issue.)
- Lee Roberts
-----Original Message-----
From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Nissim Nisimov
Sent: Friday, March 20, 2015 8:56 AM
To: Nissim Nisimov; dev at dpdk.org
Subject: Re: [dpdk-dev] Queries on DPDK working with XL710 intel NIC
Seems like the issue related to the following errors I see in dmesg:
[48459.391753] dmar: DRHD: handling fault status reg 302
[48459.392092] dmar: DMAR:[DMA Read] Request device [21:00.1] fault addr fbaddd000
[48459.392092] DMAR:[fault reason 06] PTE Read access is not set
I am running on HP ProLiant DL380p Gen8. Ubuntu 3.11.0-26-generic
Is anyone encounter this kind of issue with Intel XL710 NICs (Fortville)?
Thx
Nissim
-----Original Message-----
From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Nissim Nisimov
Sent: Thursday, March 19, 2015 7:58 PM
To: dev at dpdk.org
Subject: [dpdk-dev] Queries on DPDK working with XL710 intel NIC
Hi all,
I am trying to work with intel XL710 40GIG NIC but for some reason when trying to load it via dpdk I am getting the following error:
EAL: PCI device 0000:21:00.1 on NUMA socket 1
EAL: probe driver: 8086:1583 rte_i40e_pmd
EAL: PCI memory mapped at 0x7fff939f9000
EAL: PCI memory mapped at 0x7fffd54b8000
EAL: Error - exiting with code: 1
Cause: Requested device 0000:21:00.1 cannot be used
It seems that the "problematic" functions is i40e_aq_get_firmware_version() in the following line:
status = i40e_asq_send_command(hw, &desc, NULL, 0, cmd_details);
(gdb) p status
$3 = I40E_ERR_ADMIN_QUEUE_TIMEOUT
I did read in another mail thread (attached below) that this might be a firmware issue so i upgraded my NIC firmware version to latest but still not able to get it work:
root at lagavulin:~# ethtool -i eth24
driver: i40e
version: 1.2.37
firmware-version: f4.33.31377 a1.2 n4.42 e1932
bus-info: 0000:21:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
any idea why I still see the issue?
thanks!
Nissim
Hi Yan
Please tell me what version of firmware are you using? If it is too old, please update to at least 4.2.6.
If it is still there, check that if your firmware updating is really successful. You can try to run linux kernel driver to have a double check.
Regards,
Helin
From: Yan Freedland [mailto:YanF at Radware.com<http://dpdk.org/ml/listinfo/dev>]
Sent: Thursday, March 19, 2015 12:28 AM
To: Zhang, Helin
Cc: dev at dpdk.org<http://dpdk.org/ml/listinfo/dev>
Subject: [dpdk-dev] i40e_aq_get_firmware_version failure
Hi,
I am trying to start DPDK with 40G Intel NIC and get a failure at initialization stage in i40e_aq_get_firmware_version(). For some reason this function reaches TIMEOUT for more than maximum allowed times (10 times). In the note below I understand that several failures may be considerable but not as many as I have.
Should I enlarge the retries number ?
Is it a HW issue ?
Anyone who faced it or may assist please comment.
Thanks,
Yan
More information about the dev
mailing list