From nobody Fri Mar 25 17:21:26 2022 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 157641A30928 for <bugs@mlmmj.nyi.freebsd.org>; Fri, 25 Mar 2022 17:21:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KQ85L6XPsz3q8J for <bugs@FreeBSD.org>; Fri, 25 Mar 2022 17:21:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id BD1E711011 for <bugs@FreeBSD.org>; Fri, 25 Mar 2022 17:21:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 22PHLQXP016198 for <bugs@FreeBSD.org>; Fri, 25 Mar 2022 17:21:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 22PHLQ3r016197 for bugs@FreeBSD.org; Fri, 25 Mar 2022 17:21:26 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262658] Mellanox ConnectX-3 Pro Initialization error Date: Fri, 25 Mar 2022 17:21:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jSML4ThWwBID69YC@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-262658-227-ntfEVdbyjG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262658-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262658-227@https.bugs.freebsd.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports <freebsd-bugs.freebsd.org> List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: <mailto:freebsd-bugs+help@freebsd.org> List-Post: <mailto:freebsd-bugs@freebsd.org> List-Subscribe: <mailto:freebsd-bugs+subscribe@freebsd.org> List-Unsubscribe: <mailto:freebsd-bugs+unsubscribe@freebsd.org> Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1648228886; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Z5PvRKYVPf72ck3XXj7Cz1UiRqqYe2yPd2y2xSHgirE=; b=k5xAeD4pka8qacs3gjRpiMmGMCDGW+eL8LdoEH2hryUpGqvp8hfNDdNmBg2Zxk6rFa2N8U QXyV6OaLZChYzl1f+07Tzf/83gG4kmO1BF2IA+lAdmY0gvJ+TMUVqcXP7v7iEFIIEn7Zcb SHl67STYIMYZ8n8XLTt/Pne/CZD5m6YEP6SGIKF+0Zvt3tMuic+2n2xbx/6XxVaIdsf2HY 3ydDJtPIdSdweZ8yNsZmMTPiR7LH9RoGWftY2ZsZYSrh5mOtID3jZsvnybpyC2Y4gP95fH v6lfIAc17YzPt+HiqkPsG5iTyiRSw8ePgQ5bskyW0+20wBV4Bb2c6TsIQqFMsA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1648228886; a=rsa-sha256; cv=none; b=LOOSWwcF6eI3sFgLvIJh7HMWqInh78AA9ON30sVOxuM5EsWpBhOZpvhefdOcWc6fIhvi33 nurrtzCJjfiLeBGIExi+utMR7aZTc+23FLeiZ2nwA/koG4/dALfYWTANfDnGCXkOrbbUGB 9FWuLuFgJg5HjOEgGTFQwUKaXqysBqYyswUAuo4TpLc+SVWRE8ZeFHmIB/g/mpPT2DhL1S kd2qOxYg1h6yZA5zrLurhvb3ldAMpx1aDg3S476xIPMpz6h9/zaau1EQ2+2Oe8uNEAsZau Dl167rZycMas61pLY08zcv8eA3404V2cKBO3thhVT+5fC8sKiB3CS4bOvI57WQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262658 --- Comment #3 from jSML4ThWwBID69YC@protonmail.com --- (In reply to Hans Petter Selasky from comment #1) Firmware updated today to latest releases. The issue is still present and s= till random.=20 Dell PowerEdge R340 BIOS Version: 2.8.3 See attached screenshot for other firmware version information.=20 Mellanox data # mst status MST devices: ------------ pci0:3:0:0 - MT27520 Family [ConnectX-3 Pro] # flint -d pci0:3:0:0 q Image type: FS2 FW Version: 2.42.5000 FW Release Date: 5.9.2017 Product Version: 02.42.50.00 Rom Info: type=3DPXE version=3D3.4.752 Device ID: 4103 Description: Node Port1 Port2 S= ys image GUIDs: ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff=20 MACs: 0002c9b5e4e0 0002c9b5e4e1 VSD:=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 PSID: MT_1090111023 Dmesg output when it fails.=20 mlx4_core0: <mlx4_core> mem 0x92200000-0x922fffff,0x91000000-0x917fffff at device 0.0 on pci3 mlx4_core: Mellanox ConnectX core driver v3.6.0 (December 2020) mlx4_core: Initializing mlx4_core mlx4_core0: command 0xfff failed: fw status =3D 0x1 mlx4_core0: MAP_FA command failed, aborting mlx4_core0: Failed to start FW, aborting mlx4_core0: Failed to init fw, aborting. device_attach: mlx4_core0 attach returned 5 ichsmb0: <Intel Cannon Lake SMBus controller> port 0xefa0-0xefbf mem 0x92512000-0x925120ff at device 31.4 on pci0 smbus0: <System Management Bus> on ichsmb0 mlx4_core0: <mlx4_core> mem 0x92200000-0x922fffff,0x91000000-0x917fffff at device 0.0 on pci3 mlx4_core: Initializing mlx4_core mlx4_core0: command 0xfff failed: fw status =3D 0x1 mlx4_core0: MAP_FA command failed, aborting mlx4_core0: Failed to start FW, aborting mlx4_core0: Failed to init fw, aborting. device_attach: mlx4_core0 attach returned 5 Dmesg output when it succeeds.=20 mlx4_core0: <mlx4_core> mem 0x92200000-0x922fffff,0x91000000-0x917fffff at device 0.0 on pci3 mlx4_core: Mellanox ConnectX core driver v3.6.0 (December 2020) mlx4_core: Initializing mlx4_core mlx4_core0: Unable to determine PCI device chain minimum BW mlx4_en mlx4_core0: Activating port:1 mlxen0: Ethernet address: 00:02:c9:b5:e4:e0 mlx4_en: mlx4_core0: Port 1: Using 4 TX rings mlxen0: link state changed to DOWN mlx4_en: mlx4_core0: Port 1: Using 8 RX rings mlx4_en: mlxen0: Using 4 TX rings mlx4_en: mlxen0: Using 8 RX rings mlx4_en: mlxen0: Initializing port mlx4_en mlx4_core0: Activating port:2 mlxen1: Ethernet address: 00:02:c9:b5:e4:e1 mlx4_en: mlx4_core0: Port 2: Using 4 TX rings mlxen1: link state changed to DOWN mlx4_en: mlx4_core0: Port 2: Using 8 RX rings mlx4_en: mlxen1: Using 4 TX rings mlx4_en: mlxen1: Using 8 RX rings mlx4_en: mlxen1: Initializing port I've set the boot protocol to none to disable PXE with this:=20 mlxconfig -d pci0:3:0:0 set LEGACY_BOOT_PROTOCOL_P1=3Dnone mlxconfig -d pci0:3:0:0 set LEGACY_BOOT_PROTOCOL_P2=3Dnone This on FreeBSD 13.0-RELEASE P8. --=20 You are receiving this mail because: You are the assignee for the bug.=