From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C4BBCA0C4D; Fri, 13 Aug 2021 18:04:53 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8C8414069C; Fri, 13 Aug 2021 18:04:53 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 8E95340140 for ; Fri, 13 Aug 2021 18:04:52 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 68233A0C4E; Fri, 13 Aug 2021 18:04:52 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Fri, 13 Aug 2021 16:04:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 21.08 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cfb@hpe.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 791] Broadcom N2100G NIC does not reset after use X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D791 Bug ID: 791 Summary: Broadcom N2100G NIC does not reset after use Product: DPDK Version: 21.08 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: cfb@hpe.com Target Milestone: --- The Broadcom N2100G NIC (2x100G OCP 3.0 version) can only be used once afte= r a reboot. It appears that when testpmd shuts down, it leaves the NIC in a sta= te that subsequent uses show it to be in use. A reboot clears this condition. To duplicate: Bind the vfio-pci driver to the NIC Run a test using testpmd (interactive or non-interactive - I was using non-interactive) Stop the test Run the test a second time Error -22 will occur when trying to open the ports Output from test: Configuring Port 0 (socket 0) bnxt_hwrm_port_phy_cfg(): error 2:0:00000000:0000 bnxt_set_hwrm_link_config(): Set link config failed with rc -22 bnxt_update_phy_setting(): Failed to update PHY settings Fail to start port 0: Invalid argument Configuring Port 1 (socket 0) bnxt_hwrm_port_phy_cfg(): error 2:0:00000000:0000 bnxt_set_hwrm_link_config(): Set link config failed with rc -22 bnxt_update_phy_setting(): Failed to update PHY settings Fail to start port 1: Invalid argument Please stop the ports first Done No commandline core given, start packet forwarding Not all ports were started I have tried unbinding vfio-pci and binding bnxt_en. I have also tried stopping the ports from testpmd in interactive mode. Neither clears the condition, only a reboot does. Comments from previous patches indicate the OCP card can only be modified by the BMC. This is not an issue with the P2100G (standup PCIe NIC) This has been verified on DPDK 21.02, 21.05, and 21.08 Test system is an HPE DL385 dual AMD Milan processors F/W on the NIC is current (218.0.219.21) lspci output for port 0: 43:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57508 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb Ethernet (rev 11) Subsystem: Broadcom Inc. and subsidiaries NetXtreme-E Dual-port 100G QSFP56 Ethernet OCP 3.0 Adapter (BCM957508-N2100G) Physical Slot: 10 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- Capabilities: [160 v1] Virtual Channel Caps: LPEVC=3D0 RefClk=3D100ns PATEntryBits=3D1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=3DFixed Status: InProgress- VC0: Caps: PATOffset=3D00 MaxTimeSlots=3D1 RejSnoopTra= ns- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR25= 6- Ctrl: Enable+ ID=3D0 ArbSelect=3DFixed TC/VC=3Dff Status: NegoPending- InProgress- Capabilities: [180 v1] Vendor Specific Information: ID=3D0000 Rev= =3D0 Len=3D020 Capabilities: [1b0 v1] Latency Tolerance Reporting Max snoop latency: 1048576ns Max no snoop latency: 1048576ns Capabilities: [1b8 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 1 ARICtl: MFVC- ACS-, Function Group: 0 Capabilities: [1c0 v1] Single Root I/O Virtualization (SR-IOV) IOVCap: Migration-, Interrupt Message Number: 000 IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy+ IOVSta: Migration- Initial VFs: 8, Total VFs: 8, Number of VFs: 0, Function Dependency Link: 00 VF offset: 256, stride: 1, Device ID: 1806 Supported Page Size: 000005ff, System Page Size: 00000001 Region 0: Memory at 00000000ae2b0000 (64-bit, prefetchable) Region 2: Memory at 0000000000000000 (64-bit, prefetchable) Region 4: Memory at 00000000ae230000 (64-bit, prefetchable) VF Migration: offset: 00000000, BIR: 0 Capabilities: [230 v1] Transaction Processing Hints Interrupt vector mode supported Device specific mode supported Steering table in MSI-X table Capabilities: [300 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn-, PerformEqu- LaneErrStat: 0 Capabilities: [200 v1] Precision Time Measurement PTMCap: Requester:+ Responder:- Root:- PTMClockGranularity: Unimplemented PTMControl: Enabled:- RootSelected:- PTMEffectiveGranularity: Unknown Capabilities: [358 v1] Physical Layer 16.0 GT/s Capabilities: [388 v1] Lane Margining at the Receiver Kernel driver in use: vfio-pci Kernel modules: bnxt_en --=20 You are receiving this mail because: You are the assignee for the bug.=