[Bug 281469] Lock issue during boot.
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281469] Lock order reversal in mlx5 during boot."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281469] Lock order reversal in mlx5 during boot."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281469] Lock order reversal in mlx5 during boot."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281469] Lock order reversal in mlx5 during boot."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281469] Lock order reversal in mlx5 during boot."
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 12 Sep 2024 19:04:34 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281469
Bug ID: 281469
Summary: Lock issue during boot.
Product: Base System
Version: 14.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: crb@ChrisBowman.com
Created attachment 253527
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253527&action=edit
full dmesg output
I built a brand new EPYC system and installed a clean 14.1 with a slightly
modified
GENERIC kernel to remove devices I don't really need.
I get the following during boot:
mce0: link state changed to UP
Invoking IPv6 network device address event may sleep with the following
non-sleepable locks held:
exclusive sleep mutex mlx5rx (network driver) r = 0 (0xfffffe037ea6afc0) locked
@ /usr/src/sys/dev/mlx5/mlx5_en/mlx5_en_rx.c:654
stack backtrace:
#0 0xffffffff80bc4a9c at witness_debugger+0x6c
#1 0xffffffff80bc5c93 at witness_warn+0x403
#2 0xffffffff80d79a71 at in6_update_ifa+0xc81
#3 0xffffffff80da6220 at in6_ifadd+0x1e0
#4 0xffffffff80da2945 at nd6_ra_input+0x1025
#5 0xffffffff80d738c4 at icmp6_input+0x5b4
#6 0xffffffff80d8d0d0 at ip6_input+0xc70
#7 0xffffffff80caa1ad at netisr_dispatch_src+0xad
#8 0xffffffff80c8c94a at ether_demux+0x16a
#9 0xffffffff80c8e02d at ether_nh_input+0x3cd
#10 0xffffffff80caa1ad at netisr_dispatch_src+0xad
#11 0xffffffff80c8cda5 at ether_input+0xe5
#12 0xffffffff80d4c6ec at tcp_lro_flush_all+0xdc
#13 0xffffffff80e49a4d at mlx5e_rx_cq_comp+0x11fd
#14 0xffffffff80e049e4 at mlx5_cq_completion+0x74
#15 0xffffffff80e078bd at mlx5_eq_int+0x2ad
#16 0xffffffff80e07135 at mlx5_msix_handler+0x15
#17 0xffffffff80deff39 at lkpi_irq_handler+0x29
lock order reversal: (sleepable after non-sleepable)
1st 0xfffffe037ea6afc0 mlx5rx (network driver, sleep mutex) @
/usr/src/sys/dev/mlx5/mlx5_en/mlx5_en_rx.c:654
2nd 0xffffffff81cda7a0 in6_multi_sx (in6_multi_sx, sx) @
/usr/src/sys/netinet6/in6_mcast.c:1217
lock order network driver -> in6_multi_sx attempted at:
#0 0xffffffff80bc466d at witness_checkorder+0xbbd
#1 0xffffffff80b5a7cd at _sx_xlock+0x5d
#2 0xffffffff80d821b1 at in6_joingroup+0x31
#3 0xffffffff80d79e24 at in6_update_ifa+0x1034
#4 0xffffffff80da6220 at in6_ifadd+0x1e0
#5 0xffffffff80da2945 at nd6_ra_input+0x1025
#6 0xffffffff80d738c4 at icmp6_input+0x5b4
#7 0xffffffff80d8d0d0 at ip6_input+0xc70
#8 0xffffffff80caa1ad at netisr_dispatch_src+0xad
#9 0xffffffff80c8c94a at ether_demux+0x16a
#10 0xffffffff80c8e02d at ether_nh_input+0x3cd
#11 0xffffffff80caa1ad at netisr_dispatch_src+0xad
#12 0xffffffff80c8cda5 at ether_input+0xe5
#13 0xffffffff80d4c6ec at tcp_lro_flush_all+0xdc
#14 0xffffffff80e49a4d at mlx5e_rx_cq_comp+0x11fd
#15 0xffffffff80e049e4 at mlx5_cq_completion+0x74
#16 0xffffffff80e078bd at mlx5_eq_int+0x2ad
#17 0xffffffff80e07135 at mlx5_msix_handler+0x15
A full dmesg output is attached.
This system seems to run fairly stably after booting.
--
You are receiving this mail because:
You are the assignee for the bug.