[Bug 264583] mlx4en(4): Mellanox ConnectX-2 10g not working in 13.1-RELEASE (fine on 13.0-RELEASE)
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 10 Jun 2022 02:56:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264583
Mark Felder <feld@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |Not A Bug
Status|Open |Closed
--- Comment #5 from Mark Felder <feld@FreeBSD.org> ---
This is now coming up for me every boot, so I think the firmware update is the
fix.
Useful notes for future explorers:
1. Use the sysutils/mstflint package
2. You can get the board and firmware version from sysctl. e.g.,
> sysctl sys.device.mlx4_core0
sys.device.mlx4_core0.hw.board_id: MT_0F60110010
sys.device.mlx4_core0.hw.fw_version: 2.9.1200
sys.device.mlx4_core0.mlx4_port1_mtu: 4096
sys.device.mlx4_core0.mlx4_port1: eth
3. The mstflint examples for Linux show the device ID formatted like:
> mstflint -d 02:00.0 q
On FreeBSD the pciconf output may show the following:
mlx4_core0@pci0:1:0:0: class=0x020000 rev=0xb0 hdr=0x00 vendor=0x15b3
device=0x6750 subvendor=0x15b3 subdevice=0x0015
The correct device ID is pci0:1:0:0, so the command would be as follows:
> mstflint -d pci0:1:0:0 q
Hope this helps. Closing, I don't think this is a kernel bug anymore.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.