Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #73135

Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709

From Salvatore Bonaccorso <carnil@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709
Date 2021-09-30 17:10 +0200
Message-ID <D35R8-14B-9@gated-at.bofh.it> (permalink)
References (7 earlier) <CGlrX-3OS-1@gated-at.bofh.it> <CwPKG-60E-3@gated-at.bofh.it> <CIKme-37N-1@gated-at.bofh.it> <CwPKG-60E-3@gated-at.bofh.it> <CIKme-37N-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Hi,

On Thu, Aug 05, 2021 at 01:58:50PM +0200, spi@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

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-07-03 17:30 +0200
  Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Sebastian Piecha <sebastian@piecha.net> - 2021-07-03 18:30 +0200
  Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Salvatore Bonaccorso <carnil@debian.org> - 2021-07-05 15:00 +0200
    Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-07-05 15:10 +0200
    Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-07-10 19:00 +0200
      Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Salvatore Bonaccorso <carnil@debian.org> - 2021-07-10 22:00 +0200
        Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-07-13 15:30 +0200
          Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Salvatore Bonaccorso <carnil@debian.org> - 2021-07-14 11:30 +0200
          Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Salvatore Bonaccorso <carnil@debian.org> - 2021-07-14 11:40 +0200
            Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-07-17 20:40 +0200
              Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Salvatore Bonaccorso <carnil@debian.org> - 2021-07-29 23:10 +0200
                Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-08-05 14:10 +0200
                Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Salvatore Bonaccorso <carnil@debian.org> - 2021-09-30 17:10 +0200
                Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-10-09 13:30 +0200
                Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 Hans van Kranenburg <hans@knorrie.org> - 2021-09-30 22:20 +0200
                Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 spi@gmxpro.de - 2021-10-09 13:40 +0200
  Processed: Re: Bug#990642: linux-image-4.19.0-17-amd64: kernel  panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-07-05 15:00 +0200
  Processed: Re: Bug#990642: linux-image-4.19.0-17-amd64: kernel  panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-07-10 22:00 +0200

csiph-web