Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
21391 Discussions

I350 igb driver failed with error -2

patsch
Beginner
315 Views

Dear Support,

My setup is the following, I have a I350 connected to an arm based board (Jetson) over PCIe. On port0 of the I350 there is an external PHY (DP83TG721) connected over SGMII (rx/tx and MDIO). The external PHY is needed for automotive Ethernet.

I got the EEPROM Access tool and the accompanying  flash images. The I350 gets discovered as a PCIe device and I'm able to flash it using the EEPROM tool.

When trying the I350_2-4port_Copper_NO-MNG_1_63 flash image. The igb driver loads correctly and 4 working network interfaces appear, nice.

But the goal is to also get the external PHY working. When trying the I350_2-4port_SGMII_NO-MNG_1_63 flash image for SGMII connection with the PHY the driver fails to load

nvidia@nvidia-desktop:~$ sudo dmesg | grep igb
[ 0.217490] igb: Intel(R) Gigabit Ethernet Network Driver
[ 0.217495] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 0.217520] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[ 0.217526] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[ 14.102105] igb 0005:01:00.0: Adding to iommu group 57
[ 14.102411] igb 0005:01:00.0: enabling device (0000 -> 0002)
[ 14.755600] igb: probe of 0005:01:00.0 failed with error -2
[ 14.757712] igb 0005:01:00.1: Adding to iommu group 57
[ 14.757927] igb 0005:01:00.1: enabling device (0000 -> 0002)
[ 15.074173] igb: probe of 0005:01:00.1 failed with error -2
[ 15.074709] igb 0005:01:00.2: Adding to iommu group 57
[ 15.074889] igb 0005:01:00.2: enabling device (0000 -> 0002)
[ 15.815347] igb: probe of 0005:01:00.2 failed with error -2
[ 15.815633] igb 0005:01:00.3: Adding to iommu group 57
[ 15.815756] igb 0005:01:00.3: enabling device (0000 -> 0002)
[ 16.556610] igb: probe of 0005:01:00.3 failed with error -2

While the driver fails the I350 remains discoverable on PCIe

nvidia@nvidia-desktop:~$ sudo lspci -v

...

0005:01:00.0 Ethernet controller: Intel Corporation I350 Gigabit Connection (rev 01)
Flags: fast devsel, IRQ 203, IOMMU group 57
Memory at 2b28000000 (32-bit, non-prefetchable) [size=128K]
I/O ports at 200000 [disabled] [size=32]
Memory at 2b28080000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable- Count=10 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 02-00-00-ff-ff-aa-bb-cc
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1a0] Transaction Processing Hints
Capabilities: [1c0] Latency Tolerance Reporting
Capabilities: [1d0] Access Control Services

...

What could be causing the igb driver to fail when using the SGMII config?

To communicate with the external PHY I want to use the MDIO pass-through, are there any additional steps needed to configure this ?

Thank you for any support and insight

Labels (2)
2 Replies
patsch
Beginner
286 Views

Hey any updates regarding this topic?
I would appreciate any kind of support or info if the post is marked correctly

0 Kudos
Simon-Intel
Employee
207 Views

Hi Patryk,


Thank you for reaching out to Intel support.


Since we already have case 06534242 open for your query, we will proceed to archive the case associated with this community thread.


However, you will still be able to receive responses from our community contributors.


Best regards,

Simon

Intel Customer Support Technician


0 Kudos
Reply