Date: Fri, 10 Jun 2022 02:56:12 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 264583] mlx4en(4): Mellanox ConnectX-2 10g not working in 13.1-RELEASE (fine on 13.0-RELEASE) Message-ID: <bug-264583-7501-0SoMZFy9gF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264583-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-264583-7501@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=3D264583 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=3D0x020000 rev=3D0xb0 hdr=3D0x00 vendor=3D0x1= 5b3 device=3D0x6750 subvendor=3D0x15b3 subdevice=3D0x0015 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. --=20 You are receiving this mail because: You are on the CC list for the bug. 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-264583-7501-0SoMZFy9gF>