Hi Folks,

Can someone provide guidance on why igb probe failed? It is not clear by
code walk why igb_probe
<https://opengrok-evo.juniper.net/source/s?refs=igb_probe&project=ker-linux-v5.15-unified>()
is failing and returning -2.

>>
Jan 06 05:05:44 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: working
around ROM BAR overlap defect
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0:
[8086:1538] type 00 class 0x020000
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: reg
0x10: [mem 0x90400000-0x904fffff]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: reg
0x18: [io  0x1000-0x101f]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: reg
0x1c: [mem 0x90500000-0x90503fff]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: reg
0x30: [mem 0x90500000-0x905fffff pref]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: PME#
supported from D0 D3hot D3cold
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0:
of_pci_add_device: re-using pre-set node
@/pci-0000-00/pci-0000-00-17.0/pci-0000-0a-00.0
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: BAR 0:
assigned [mem 0x90400000-0x904fffff]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: BAR 6:
assigned [mem 0x90500000-0x905fffff pref]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: BAR 3:
no space for [mem size 0x00004000]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: BAR 3:
failed to assign [mem size 0x00004000]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: pci 0000:0a:00.0: BAR 2:
assigned [io  0x1000-0x101f]
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: bus: 'pci':
__driver_probe_device: matched device 0000:0a:00.0 with driver igb
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: bus: 'pci': really_probe:
probing driver igb with device 0000:0a:00.0
Jan 06 05:05:45 mclaren-ptx-diags-a1-re1 kernel: igb: probe of 0000:0a:00.0
failed with error -2

Logs of reference working router (RE0) - similar firmware and configuration.

===============================================================



[vrf:none] root@mclaren-ptx-diags-a1-re0:~# journalctl -b0 | grep 0a:00.0

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: working
around ROM BAR overlap defect

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0:
[8086:1538] type 00 class 0x020000

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: reg
0x10: [mem 0x90400000-0x904fffff]

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: reg
0x18: [io  0x1000-0x101f]

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: reg
0x1c: [mem 0x90500000-0x90503fff]

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: reg
0x30: [mem 0xfff00000-0xffffffff pref]

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: PME#
supported from D0 D3hot D3cold

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: can't
claim BAR 6 [mem 0xfff00000-0xffffffff pref]: no compatible bridge window

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: BAR 6:
no space for [mem size 0x00100000 pref]

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: pci 0000:0a:00.0: BAR 6:
failed to assign [mem size 0x00100000 pref]

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0: added
PHC on eth0

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0: Intel(R)
Gigabit Ethernet Network Connection

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0: eth0:
(PCIe:2.5Gb/s:Width x1) 00:a0:c9:00:00:00

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0: eth0:
PBA No: 000500-000

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0: Using
MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)

Jan 05 18:45:27 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0 eth0:
igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Jan 05 18:45:32 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0 eth0:
igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Jan 05 18:45:39 mclaren-ptx-diags-a1-re0 kernel: igb 0000:0a:00.0 eth0:
igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX



[vrf:none] root@mclaren-ptx-diags-a1-re0:~# lspci -vvvv -s 0a:00.0

0a:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network
Connection (rev 03)

        Physical Slot: 11

        Device tree node:
/sys/firmware/devicetree/base/pci-0000-00/pci-0000-00-17.0/pci-0000-0a-00.0

        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping- SERR+ FastB2B- DisINTx+

        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

        Latency: 0, Cache Line Size: 64 bytes

        Interrupt: pin A routed to IRQ 16

        NUMA node: 0

        Region 0: Memory at 90400000 (32-bit, non-prefetchable) [size=1M]

        Region 2: I/O ports at 1000 [size=32]

        Region 3: Memory at 90500000 (32-bit, non-prefetchable) [size=16K]

        Expansion ROM at <ignored> [disabled]

        Capabilities: [40] Power Management version 3

                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)

                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-

        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+

                Address: 0000000000000000  Data: 0000

                Masking: 00000000  Pending: 00000000

        Capabilities: [70] MSI-X: Enable+ Count=5 Masked-

                Vector table: BAR=3 offset=00000000

                PBA: BAR=3 offset=00002000

        Capabilities: [a0] Express (v2) Endpoint, MSI 00

                DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s
<512ns, L1 <64us

                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
SlotPowerLimit 0.000W

                DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+

                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
FLReset-

                        MaxPayload 256 bytes, MaxReadReq 512 bytes

                DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+
TransPend-

                LnkCap: Port #3, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit
Latency L0s <2us, L1 <16us

                        ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+

                LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+

                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

                LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)

                        TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

                DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
NROPrPrP- LTR-

                         10BitTagComp- 10BitTagReq- OBFF Not Supported,
ExtFmt- EETLPPrefix-

                         EmergencyPowerReduction Not Supported,
EmergencyPowerReductionInit-

                         FRS- TPHComp- ExtTPHComp-

                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-

                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR-
OBFF Disabled,

                         AtomicOpsCtl: ReqEn-

                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
SpeedDis-

                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-

                         Compliance De-emphasis: -6dB

                LnkSta2: Current De-emphasis Level: -6dB,
EqualizationComplete- EqualizationPhase1-

                         EqualizationPhase2- EqualizationPhase3-
LinkEqualizationRequest-

                         Retimer- 2Retimers- CrosslinkRes: unsupported

        Capabilities: [100 v2] Advanced Error Reporting

                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-

                UESvrt: DLP+ SDES+ TLP+ FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-

                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
AdvNonFatalErr-

                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
AdvNonFatalErr-

                AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn-
ECRCChkCap+ ECRCChkEn-

                        MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-

                HeaderLog: 00000000 00000000 00000000 00000000

        Capabilities: [140 v1] Device Serial Number 00-a0-c9-ff-ff-00-00-00

        Capabilities: [1a0 v1] Transaction Processing Hints

                Device specific mode supported

                Steering table in TPH capability structure

        Kernel driver in use: igb



[vrf:none] root@mclaren-ptx-diags-a1-re0:~# ethtool -i eth0

driver: igb

version: 5.15.164-10.22.33.18-yocto-stan

firmware-version: 3.30, 0x8000076e

expansion-rom-version:

bus-info: 0000:0a:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

[vrf:none] root@mclaren-ptx-diags-a1-re0:~# ethtool  eth0

Settings for eth0:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Supported FEC modes: Not reported

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: Yes

        Advertised FEC modes: Not reported

        Speed: 1000Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 5

        Transceiver: internal

        Auto-negotiation: on

        MDI-X: on (auto)

        Supports Wake-on: pumbg

        Wake-on: g

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes
>>

Regards,

-sam

_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel Ethernet, visit 
https://community.intel.com/t5/Ethernet-Products/bd-p/ethernet-products

Reply via email to