[Bug 262658] Mellanox ConnectX-3 Pro Initialization error
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262658] Mellanox ConnectX-3 Pro Initialization error"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262658] Mellanox ConnectX-3 Pro Initialization error"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262658] Mellanox ConnectX-3 Pro Initialization error"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262658] Mellanox ConnectX-3 Pro Initialization error"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262658] Mellanox ConnectX-3 Pro Initialization error"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 19 Mar 2022 03:26:49 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262658 Bug ID: 262658 Summary: Mellanox ConnectX-3 Pro Initialization error Product: Base System Version: 13.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jSML4ThWwBID69YC@protonmail.com The Mellanox ConnectX-3 Pro network card does not initialize some of the time when in a Dell R340 server. Sometimes it works on boot, sometimes it fails. It seems completely random, though it fails more often than it succeeds. If it fails at boot, it won't load by unloading/reloading the driver with kldunload/kldload. The same ConnectX-3 cards in a different server work 100% of the time, so I suspect it has something to do with it being in a Dell R340. Server hardware: Dell PowerEdge R340 pciconf -lv none7@pci0:3:0:0: class=0x020000 rev=0x00 hdr=0x00 vendor=0x15b3 device=0x1007 subvendor=0x15b3 subdevice=0x0006 vendor = 'Mellanox Technologies' device = 'MT27520 Family [ConnectX-3 Pro]' class = network subclass = ethernet DMESG error mlx5en: Mellanox Ethernet driver 3.6.0 (December 2020) 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 = 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 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 = 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 -- You are receiving this mail because: You are the assignee for the bug.