Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Nov 2025 22:37:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 290793] iovctl on mlx5en won't work
Message-ID:  <bug-290793-7501-Q1n6rHtM1v@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-290793-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-290793-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=290793

--- Comment #16 from Bjoern A. Zeeb <bz@FreeBSD.org> ---
(In reply to Konstantin Belousov from comment #15)

Yes, your comment came overlapping with me typing the before already.

[3.686949] mlx5_core0: <mlx5_core> mem 0x383ffc000000-0x383ffdffffff irq 32 at
device 0.0 on pci3
[3.694355] mlx5: Mellanox Core driver 3.7.1 (November 2021)  << missing \n?
[4.061886] mlx5_core0: attempting to allocate 15 MSI-X vectors (128 supported)
..
[4.143047] mlx5_core0: using IRQs 72-86 for MSI-X
[4.166061] mlx5_core0: WARN: mlx5_vsc_set_space:125:(pid 0): Space 0x7 is not
supported.
[4.172669] mlx5_core0: WARN: mlx5_fwdump_prep:99:(pid 0): VSC scan space is not
supported
[4.179641] mlx5_core: INFO: (mlx5_core0): E-Switch: Total vports 11, l2 table
size(65536), per vport: max uc(1024) max mc(16384)
[4.225477] pci0:2:0:1: reprobing on driver added
[4.231668] mlx5_core1: <mlx5_core> mem 0x383ffa000000-0x383ffbffffff irq 32 at
device 0.1 on pci3
[4.575887] mlx5_core1: attempting to allocate 15 MSI-X vectors (128 supported)

[4.657320] mlx5_core1: using IRQs 87-101 for MSI-X
[4.685698] mlx5_core1: WARN: mlx5_vsc_set_space:125:(pid 0): Space 0x7 is not
supported.
[4.692308] mlx5_core1: WARN: mlx5_fwdump_prep:99:(pid 0): VSC scan space is not
supported
[4.699282] mlx5_core: INFO: (mlx5_core1): E-Switch: Total vports 11, l2 table
size(65536), per vport: max uc(1024) max mc(16384)

[4.773045] mce0: Ethernet address: 7c:fe:90:30:xx:xx
[4.776802] mce0: link state changed to DOWN
[4.778092] mlx5_core0: ERR: mlx5_cmd_check:714:(pid 0): ACCESS_REG(0x805)
op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48)

[4.795174] mlx5_core0: ERR: mlx5_cmd_check:714:(pid 0): ACCESS_REG(0x805)
op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48)

[4.882680] mce1: bpf attached
[4.884171] mce1: Ethernet address: 7c:fe:90:30:xx:xx
[4.887923] mce1: link state changed to DOWN
[4.889062] mlx5_core1: ERR: mlx5_cmd_check:714:(pid 0): ACCESS_REG(0x805)
op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48)
[4.906441] mlx5_core1: ERR: mlx5_cmd_check:714:(pid 0): ACCESS_REG(0x805)
op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48)


How do I update the firmware to the right version?
Sorry I am asking for extra hand holding but I figure it'll help to make
progress faster.

-- 
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-290793-7501-Q1n6rHtM1v>