Hi, On Thu, Aug 05, 2021 at 01:58:50PM +0200, s...@gmxpro.de wrote: > > In preparation for the bug report for upstream I did some more > investigation. > > The kernel panic also occurs without bonding interfaces but needs much > more time to happen. With a bonding interface it happens within some > seconds. Without bonding interfaces it needs like a minute with the > network discovery being re-launched for 2 or 3 times. The kernel panic > is still the same about the bnx2 driver. > > In the constellation without a bonding interface the kernel panic only > occurs if > - opnsense as a domU is running (this domU bounds all bridged interfaces > as default gateway for all networks) > - sysctl parameter net.bridge.bridge-nf-call-ip6tables is set to 0. > > If both conditions are not met no kernel panic oaccurs. > > Other IPv6 related sysctl parameters are set on dom0 like > net.ipv6.conf.all.disable_ipv6 = 1 > net.ipv6.conf.default.disable_ipv6 = 1 > net.ipv6.conf.lo.disable_ipv6 = 1 > > > The layer2-iptables settings are > net.bridge.bridge-nf-call-ip6tables = 0 *** > > > net.bridge.bridge-nf-call-iptables = 1 > > > net.bridge.bridge-nf-call-arptables = 0 > > > > > As said, if I don't set the one marked with *** to 0 there is no kernel > panic. > > I wonder if this still is a kernel issue but still wouldn't expect a > kernel panic to happen.
Did you got any response on your reporting upstream? Regards, Salvatore
