[Bug 264058] Mellanox ConnectX-3 10g ether not working in 13.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264058

            Bug ID: 264058
           Summary: Mellanox ConnectX-3 10g ether not working in 13.1
           Product: Base System
           Version: 13.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: crb@ChrisBowman.com

I had a 13.0 system fully working.  It has a Mellanox 10g ether card
(ConnectX-3 I think) that worked without issue.  I replaced the SSD and
installed 13.1 and now the card doesn't work.  It shows up in dmesg:

mlx4_core0: mlx4_shutdown was called
mlx4_core0: <mlx4_core> mem 0xfb700000-0xfb7fffff,0x7fff800000-0x7fffffffff irq
30 at device 0.0 on pci4
mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021)
mlx4_core: Initializing mlx4_core
mlx4_core0: Unable to determine PCI device chain minimum BW
mlx4_core0: mlx4_shutdown was called
mlx4_core0: <mlx4_core> mem 0xfb700000-0xfb7fffff,0x7fff800000-0x7fffffffff irq
30 at device 0.0 on pci4
mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021)
mlx4_core: Initializing mlx4_core
mlx4_core0: Unable to determine PCI device chain minimum BW
mlx4_core0: mlx4_shutdown was called
mlx4_core0: <mlx4_core> mem 0xfb700000-0xfb7fffff,0x7fff800000-0x7fffffffff irq
30 at device 0.0 on pci4
mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021)
mlx4_core: Initializing mlx4_core
mlx4_core0: Unable to determine PCI device chain minimum BW

But doesn't show up in ifconfig:

crb@eclipse:294> ifconfig -a
em0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=481049b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LRO,VLAN_HWFILTER,NOMAP>
        ether 00:1b:21:1d:12:ad
        inet6 fe80::21b:21ff:fe1d:12ad%em0 prefixlen 64 scopeid 0x1
        inet6 2600:1700:5430:10b1:21b:21ff:fe1d:12ad prefixlen 64 autoconf
        inet 192.168.1.190 netmask 0xffffff00 broadcast 192.168.1.255
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
igc0: flags=8822<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
        ether 3c:7c:3f:4e:0b:c6
        media: Ethernet autoselect
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

I'm happy to build kernels, debug what ever is necessary to help fix the
problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.