Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Mar 2022 17:21:26 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 262658] Mellanox ConnectX-3 Pro Initialization error
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/>

next in thread | previous in thread | raw e-mail | index | archive | help
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262658-227-ntfEVdbyjG>