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

Groups > linux.debian.kernel > #72346 > unrolled thread

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

Started byspi@gmxpro.de
First post2021-07-03 17:30 +0200
Last post2021-07-10 22:00 +0200
Articles 18 — 5 participants

Back to article view | Back to linux.debian.kernel

Contents

  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

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

Fromspi@gmxpro.de
Date2021-07-03 17:30 +0200
SubjectBug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709
Message-ID<CwPKG-60E-3@gated-at.bofh.it>
Package: src:linux
Version: 4.19.194-1
Severity: important



-- Package-specific info:
** Version:
Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-1 (2021-06-10)

** Command line:
placeholder root=/dev/mapper/srvxen04-root ro console=ttyS0,115200n8
console=tty0 intel_iommu=on nomodeset net.ifnames=1 biosdevname=0

** Not tainted

** Kernel log:
[   39.592859] vif vif-1-0 vif-fw2-OAM: renamed from vif1.0
[   39.620827] vif vif-1-3 vif-fw2-FE: renamed from vif1.3
[   39.648849] vif vif-1-2 vif-fw2-DMZ0: renamed from vif1.2
[   39.676964] vif vif-1-6 vif-fw2-TEST: renamed from vif1.6
[   39.712828] vif vif-1-8 vif-fw2-HOME: renamed from vif1.8
[   39.796755] brLAN: port 2(vif-fw2-LAN) entered blocking state
[   39.802908] brLAN: port 2(vif-fw2-LAN) entered disabled state
[   39.809479] device vif-fw2-LAN entered promiscuous mode
[   39.815267] brOAM: port 2(vif-fw2-OAM) entered blocking state
[   39.821493] brOAM: port 2(vif-fw2-OAM) entered disabled state
[   39.827692] device vif-fw2-OAM entered promiscuous mode
[   39.833365] brWLAN: port 2(vif-fw2-WLAN) entered blocking state
[   39.839769] brWLAN: port 2(vif-fw2-WLAN) entered disabled state
[   39.846161] device vif-fw2-WLAN entered promiscuous mode
[   39.851967] brDMZ0: port 2(vif-fw2-DMZ0) entered blocking state
[   39.858295] brDMZ0: port 2(vif-fw2-DMZ0) entered disabled state
[   39.864659] device vif-fw2-DMZ0 entered promiscuous mode
[   39.874675] brFE: port 2(vif-fw2-FE) entered blocking state
[   39.880621] brFE: port 2(vif-fw2-FE) entered disabled state
[   39.886968] device vif-fw2-FE entered promiscuous mode
[   39.893906] brRLAN: port 2(vif-fw2-RLAN) entered blocking state
[   39.900254] brRLAN: port 2(vif-fw2-RLAN) entered disabled state
[   39.907304] device vif-fw2-RLAN entered promiscuous mode
[   39.915348] brTEST: port 2(vif-fw2-TEST) entered blocking state
[   39.921718] brTEST: port 2(vif-fw2-TEST) entered disabled state
[   39.928290] device vif-fw2-TEST entered promiscuous mode
[   39.934666] brBE: port 2(vif-fw2-BE) entered blocking state
[   39.940616] brBE: port 2(vif-fw2-BE) entered disabled state
[   39.946814] device vif-fw2-BE entered promiscuous mode
[   39.953792] brHOME: port 2(vif-fw2-HOME) entered blocking state
[   39.960107] brHOME: port 2(vif-fw2-HOME) entered disabled state
[   39.966581] device vif-fw2-HOME entered promiscuous mode
[   42.160336] xen-blkback: backend/vbd/1/51712: using 1 queues,
protocol 1 (x86_64-abi)
[   42.353338] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
[   42.358612] brOAM: port 2(vif-fw2-OAM) entered blocking state
[   42.364733] brOAM: port 2(vif-fw2-OAM) entered forwarding state
[   42.378050] vif vif-1-1 vif-fw2-LAN: Guest Rx ready
[   42.383309] brLAN: port 2(vif-fw2-LAN) entered blocking state
[   42.389427] brLAN: port 2(vif-fw2-LAN) entered forwarding state
[   42.428330] vif vif-1-2 vif-fw2-DMZ0: Guest Rx ready
[   42.433682] brDMZ0: port 2(vif-fw2-DMZ0) entered blocking state
[   42.440053] brDMZ0: port 2(vif-fw2-DMZ0) entered forwarding state
[   42.448264] vif vif-1-3 vif-fw2-FE: Guest Rx ready
[   42.453429] brFE: port 2(vif-fw2-FE) entered blocking state
[   42.459409] brFE: port 2(vif-fw2-FE) entered forwarding state
[   42.467498] vif vif-1-4 vif-fw2-BE: Guest Rx ready
[   42.472669] brBE: port 2(vif-fw2-BE) entered blocking state
[   42.478647] brBE: port 2(vif-fw2-BE) entered forwarding state
[   42.486688] vif vif-1-5 vif-fw2-WLAN: Guest Rx ready
[   42.492049] brWLAN: port 2(vif-fw2-WLAN) entered blocking state
[   42.498370] brWLAN: port 2(vif-fw2-WLAN) entered forwarding state
[   42.506575] vif vif-1-6 vif-fw2-TEST: Guest Rx ready
[   42.511964] brTEST: port 2(vif-fw2-TEST) entered blocking state
[   42.518364] brTEST: port 2(vif-fw2-TEST) entered forwarding state
[   42.526458] vif vif-1-7 vif-fw2-RLAN: Guest Rx ready
[   42.531790] brRLAN: port 2(vif-fw2-RLAN) entered blocking state
[   42.538105] brRLAN: port 2(vif-fw2-RLAN) entered forwarding state
[   42.546365] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
[   42.551699] brHOME: port 2(vif-fw2-HOME) entered blocking state
[   42.557990] brHOME: port 2(vif-fw2-HOME) entered forwarding state
[   52.749924] brBE: port 2(vif-fw2-BE) entered disabled state
[   52.857180] vif vif-1-4 vif-fw2-BE: Guest Rx ready
[   52.862389] brBE: port 2(vif-fw2-BE) entered blocking state
[   52.868356] brBE: port 2(vif-fw2-BE) entered forwarding state
[   53.011574] vif vif-1-4 vif-fw2-BE: Guest Rx ready
[   53.011597] NOHZ: local_softirq_pending 08
[   53.145228] vif vif-1-3 vif-fw2-FE: Guest Rx ready
[   53.253183] vif vif-1-3 vif-fw2-FE: Guest Rx ready
[   53.253214] NOHZ: local_softirq_pending 08
[   53.377074] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
[   53.493773] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
[   53.493792] NOHZ: local_softirq_pending 08
[   53.648414] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
[   53.761142] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
[   53.761165] NOHZ: local_softirq_pending 08
[   53.948967] vif vif-1-6 vif-fw2-TEST: Guest Rx ready
[   54.059419] vif vif-1-6 vif-fw2-TEST: Guest Rx ready
[   54.059437] NOHZ: local_softirq_pending 08
[   54.197135] vif vif-1-1 vif-fw2-LAN: Guest Rx ready
[   54.308315] vif vif-1-1 vif-fw2-LAN: Guest Rx ready
[   54.308334] NOHZ: local_softirq_pending 08
[   54.445602] vif vif-1-7 vif-fw2-RLAN: Guest Rx ready
[   54.568490] vif vif-1-7 vif-fw2-RLAN: Guest Rx ready
[   54.728865] vif vif-1-5 vif-fw2-WLAN: Guest Rx ready
[   54.845130] vif vif-1-5 vif-fw2-WLAN: Guest Rx ready
[   54.845150] NOHZ: local_softirq_pending 08
[   74.929309] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
MAC=ff:ff:ff:ff:ff:ff:c4:ad:34:93:14:ea:08:00 SRC=192.168.254.18
DST=255.255.255.255 LEN=152 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
SPT=5678 DPT=5678 LEN=132
[   77.182871] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
MAC=ff:ff:ff:ff:ff:ff:00:e0:4c:68:06:cd:08:00 SRC=192.168.254.194
DST=192.168.254.255 LEN=569 TOS=0x00 PREC=0x00 TTL=64 ID=62930 DF
PROTO=UDP SPT=51786 DPT=21027 LEN=549
[   79.451615] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
MAC=ff:ff:ff:ff:ff:ff:c4:ad:34:c0:a4:e4:08:00 SRC=192.168.254.19
DST=255.255.255.255 LEN=151 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
SPT=5678 DPT=5678 LEN=131
[   83.328385] vif vif-2-0 vif-iam-BE: renamed from vif2.0
[   83.396142] brBE: port 3(vif-iam-BE) entered blocking state
[   83.402125] brBE: port 3(vif-iam-BE) entered disabled state
[   83.408134] device vif-iam-BE entered promiscuous mode
[   84.354072] xen-blkback: backend/vbd/2/51714: using 1 queues,
protocol 1 (x86_64-abi) persistent grants
[   84.370113] vif vif-2-0 vif-iam-BE: Guest Rx ready
[   84.375381] brBE: port 3(vif-iam-BE) entered blocking state
[   84.377168] xen-blkback: backend/vbd/2/51713: using 1 queues,
protocol 1 (x86_64-abi) persistent grants
[   84.381355] brBE: port 3(vif-iam-BE) entered forwarding state
[   92.005330] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
MAC=ff:ff:ff:ff:ff:ff:c4:ad:34:90:19:a4:08:00 SRC=192.168.254.16
DST=255.255.255.255 LEN=152 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
SPT=5678 DPT=5678 LEN=132
[   97.954330] iptables denied: IN=brTEST OUT= PHYSIN=bond0.200
MAC=ff:ff:ff:ff:ff:ff:40:31:3c:a7:9b:57:08:00 SRC=0.0.0.0
DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
SPT=68 DPT=67 LEN=308

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 1302
board_vendor: ASUSTeK COMPUTER INC.
board_name: P8Q77-M
board_version: Rev X.0x

** Loaded modules:
xen_netback
xen_blkback
8021q
garp
mrp
bonding
nf_log_ipv6
xen_gntdev
ip6t_REJECT
nf_reject_ipv6
xen_evtchn
xenfs
xen_privcmd
br_netfilter
bridge
stp
llc
nf_log_ipv4
nf_log_common
nft_limit
nft_counter
dm_snapshot
dm_bufio
xt_physdev
xt_LOG
xt_limit
xt_tcpudp
xt_state
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
ipt_REJECT
nf_reject_ipv4
nft_compat
nf_tables
nfnetlink
intel_powerclamp
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
mei_wdt
eeepc_wmi
asus_wmi
sparse_keymap
rfkill
wmi_bmof
pcspkr
iTCO_wdt
iTCO_vendor_support
evdev
joydev
mei_me
mei
i915
drm_kms_helper
drm
i2c_algo_bit
sg
wmi
video
button
xen_pciback
loop
sunrpc
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
fscrypto
ecb
dm_mod
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
sd_mod
hid_generic
usbhid
hid
crc32c_intel
ahci
aesni_intel
aes_x86_64
libahci
crypto_simd
cryptd
glue_helper
xhci_pci
libata
i2c_i801
lpc_ich
ehci_pci
mfd_core
mpt3sas
raid_class
ehci_hcd
xhci_hcd
scsi_transport_sas
scsi_mod
bnx2
usbcore
e1000e
usb_common
thermal
fan

** Network interface configuration:

-- System Information:
Debian Release: 10.10
   APT prefers stable
   APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-17-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod                                    26-1
ii  linux-base                              4.6

Versions of packages linux-image-4.19.0-17-amd64 recommends:
ii  apparmor             2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-4.19.0-17-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 2.02+dfsg1-20+deb10u4
ii  linux-doc-4.19          4.19.194-1

Versions of packages linux-image-4.19.0-17-amd64 is related to:
pn  firmware-amd-graphics                       <none>
pn  firmware-atheros                            <none>
ii  firmware-bnx2                               20190114-2
pn  firmware-bnx2x                              <none>
pn  firmware-brcm80211                          <none>
pn  firmware-cavium                             <none>
pn  firmware-intel-sound                        <none>
pn  firmware-intelwimax                         <none>
pn  firmware-ipw2x00                            <none>
pn  firmware-ivtv                               <none>
pn  firmware-iwlwifi                            <none>
pn  firmware-libertas                           <none>
pn  firmware-linux-nonfree                      <none>
pn  firmware-misc-nonfree                       <none>
pn  firmware-myricom                            <none>
pn  firmware-netxen                             <none>
pn  firmware-qlogic                             <none>
pn  firmware-realtek                            <none>
pn  firmware-samsung                            <none>
pn  firmware-siano                              <none>
pn  firmware-ti-connectivity                    <none>
ii  xen-hypervisor-4.11-amd64 [xen-hypervisor] 4.11.4+107-gef32c7afa2-1

-- no debconf information

### Kernel Panic

[ 2659.446701] BUG: unable to handle kernel NULL pointer dereference at
0000000000000080
[ 2659.540562] PGD 0 P4D 0
[ 2659.570927] Oops: 0000 [#1] SMP NOPTI
[ 2659.614816] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.0-17-amd64
#1 Debian 4.19.194-1
[ 2659.713823] Hardware name: System manufacturer System Product
Name/P8Q77-M, BIOS 1302 08/06/2014
[ 2659.819073] RIP: e030:bnx2_poll_work+0x61f/0x12c0 [bnx2]
[ 2659.882716] Code: 10 48 89 d7 48 81 c7 a8 00 00 00 0f 84 fb 00 00 00
48 8b 92 b8 02 00 00 48 85 d2 0f 84 eb 00 00 00 4c 8b 4a 28 4d 85 c9 74
1f <41> 8b 97 80 00 00 00 48 8b 75 08 45 31 c0 b9 01 00 00 00 41 2b 97
[ 2660.107569] RSP: e02b:ffff88803e603e08 EFLAGS: 00010286
[ 2660.170170] RAX: ffff88803095e000 RBX: 0000000000005dba RCX:
000000000000022e
[ 2660.255658] RDX: ffffffff81cc12e0 RSI: 9730aa88f5172c0a RDI:
ffff888039b110a8
[ 2660.341147] RBP: ffff88803095f170 R08: 00000000000271d0 R09:
ffffffff814a7c90
[ 2660.426636] R10: ffffea00002faa00 R11: 0000000000000000 R12:
0000000000000050
[ 2660.512123] R13: ffff8880329f88c0 R14: ffff8880329f8d80 R15:
0000000000000000
[ 2660.597617] FS:  00007fb65e0f0740(0000) GS:ffff88803e600000(0000)
knlGS:0000000000000000
[ 2660.694536] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2660.763383] CR2: 0000000000000080 CR3: 0000000031fe2000 CR4:
0000000000040660
[ 2660.848880] Call Trace:
[ 2660.878204]  <IRQ>
[ 2660.902339]  ? __napi_schedule+0x63/0x70
[ 2660.949342]  bnx2_poll_msix+0x33/0xd0 [bnx2]
[ 2661.000511]  net_rx_action+0x149/0x3b0
[ 2661.045440]  __do_softirq+0xde/0x2d8
[ 2661.088290]  irq_exit+0xba/0xc0
[ 2661.125937]  xen_evtchn_do_upcall+0x2c/0x40
[ 2661.176057]  xen_do_hypervisor_callback+0x29/0x40
[ 2661.232422]  </IRQ>
[ 2661.257587] RIP: e030:xen_hypercall_sched_op+0xa/0x20
[ 2661.318116] Code: 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc
cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f
05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
[ 2661.542969] RSP: e02b:ffffffff82003e70 EFLAGS: 00000246
[ 2661.605569] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
ffffffff810013aa
[ 2661.691057] RDX: 00000000014282fa RSI: 0000000000000000 RDI:
0000000000000001
[ 2661.776546] RBP: 0000000000000000 R08: 000000002d3bca96 R09:
0000000000000008
[ 2661.862033] R10: 0000000000007ff0 R11: 0000000000000246 R12:
0000000000000000
[ 2661.947519] R13: 0000000000000000 R14: 0000000000000000 R15:
0000000000000000
[ 2662.033012]  ? xen_hypercall_sched_op+0xa/0x20
[ 2662.086255]  ? xen_safe_halt+0xc/0x20
[ 2662.130144]  ? default_idle+0x1c/0x140
[ 2662.175070]  ? do_idle+0x1e3/0x270
[ 2662.215839]  ? cpu_startup_entry+0x6f/0x80
[ 2662.264927]  ? start_kernel+0x507/0x52a
[ 2662.310893]  ? default_get_nmi_reason+0x10/0x10
[ 2662.365181]  ? xen_start_kernel+0x5a4/0x5af
[ 2662.415308] Modules linked in: xen_netback xen_blkback 8021q garp mrp
bonding xen_gntdev nf_log_ipv6 ip6t_REJECT xen_evtchn nf_reject_ipv6
xenfs xen_privcmd br_netfilter bridge stp llc nf_log_ipv4 nf_log_common
nft_limit nft_counter xt_physdev xt_LOG xt_limit xt_tcpudp dm_snapshot
xt_state dm_bufio xt_conntrack nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 ipt_REJECT nf_reject_ipv4 nft_compat nf_tables nfnetlink
intel_powerclamp crct10dif_pclmul crc32_pclmul eeepc_wmi asus_wmi
ghash_clmulni_intel sparse_keymap mei_wdt rfkill wmi_bmof pcspkr
iTCO_wdt i915 joydev evdev iTCO_vendor_support drm_kms_helper drm mei_me
mei i2c_algo_bit sg wmi video button xen_pciback loop sunrpc ip_tables
x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb dm_mod raid10
raid456 async_raid6_recov async_memcpy async_pq async_xor
[ 2663.266470]  async_tx xor raid6_pq libcrc32c crc32c_generic raid1
raid0 multipath linear md_mod hid_generic usbhid hid sd_mod crc32c_intel
aesni_intel ahci aes_x86_64 crypto_simd cryptd libahci glue_helper
lpc_ich i2c_i801 ehci_pci libata mpt3sas xhci_pci mfd_core raid_class
xhci_hcd ehci_hcd scsi_transport_sas e1000e bnx2 usbcore scsi_mod
usb_common thermal fan
[ 2663.650520] CR2: 0000000000000080
[ 2663.691381] ---[ end trace 7a21ad49627256e7 ]---
[ 2663.746711] RIP: e030:bnx2_poll_work+0x61f/0x12c0 [bnx2]
[ 2663.810353] Code: 10 48 89 d7 48 81 c7 a8 00 00 00 0f 84 fb 00 00 00
48 8b 92 b8 02 00 00 48 85 d2 0f 84 eb 00 00 00 4c 8b 4a 28 4d 85 c9 74
1f <41> 8b 97 80 00 00 00 48 8b 75 08 45 31 c0 b9 01 00 00 00 41 2b 97
[ 2664.035208] RSP: e02b:ffff88803e603e08 EFLAGS: 00010286
[ 2664.097809] RAX: ffff88803095e000 RBX: 0000000000005dba RCX:
000000000000022e
[ 2664.183298] RDX: ffffffff81cc12e0 RSI: 9730aa88f5172c0a RDI:
ffff888039b110a8
[ 2664.268782] RBP: ffff88803095f170 R08: 00000000000271d0 R09:
ffffffff814a7c90
[ 2664.354270] R10: ffffea00002faa00 R11: 0000000000000000 R12:
0000000000000050
[ 2664.439759] R13: ffff8880329f88c0 R14: ffff8880329f8d80 R15:
0000000000000000
[ 2664.525252] FS:  00007fb65e0f0740(0000) GS:ffff88803e600000(0000)
knlGS:0000000000000000
[ 2664.622175] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2664.691021] CR2: 0000000000000080 CR3: 0000000031fe2000 CR4:
0000000000040660
[ 2664.776512] Kernel panic - not syncing: Fatal exception in interrupt
[ 2664.852642] Kernel Offset: disabled


### network controller

lspci | grep net
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
04:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
04:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
05:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
05:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
Gigabit Ethernet (rev 20)

### interface configuration

auto lo
iface lo inet loopback
auto enp4s0f0
iface enp4s0f0 inet manual
auto enp4s0f1
iface enp4s0f1 inet manual
auto enp5s0f0
iface enp5s0f0 inet manual
auto enp5s0f1
iface enp5s0f1 inet manual
auto bond0
iface bond0 inet manual
         up ifconfig bond0 0.0.0.0 up
         slaves enp5s0f1 enp5s0f0
         bond-mode 802.3ad
         bond-miimon 100
         bond-downdelay 200
         bond-updelay 200
         bond-lacp-rate fast
         bond-xmit-hash-policy layer2+3
         post-up ifconfig enp5s0f0 mtu 8996 && ifconfig enp5s0f1 mtu
8996 && ifconfig bond0 mtu 8996
auto brINT
iface brINT inet static
     pre-up brctl addbr $IFACE
     up ip link set $IFACE up
     post-down brctl delbr $IFACE
     down ip link set $IFACE down
     hwaddress ether 00:16:3E:24:00:11
     address 192.168.240.11
     network 192.168.240.0
     netmask 255.255.255.0
     broadcast 192.168.240.255
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
auto brOAM
auto brLAN
iface bond0.50 inet manual
auto brWLAN
iface bond0.100 inet manual
auto brHOME
iface bond0.101 inet manual
auto brRLAN
iface bond0.255 inet manual
auto brTEST
iface bond0.200 inet manual
auto brBE
iface bond0.70 inet manual
auto brFE
iface bond0.201 inet manual
auto brDMZ0
iface enp4s0f0 inet manual
iface brOAM inet static
     address 192.168.254.11
     network 192.168.254.0
     netmask 255.255.255.0
     broadcast 192.168.254.255
     gateway 192.168.254.1
     dns-nameservers 192.168.254.1
     bridge_ports enp4s0f1
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brLAN inet manual
     bridge_ports bond0.50
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brWLAN inet manual
     bridge_ports bond0.100
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brHOME inet manual
     bridge_ports bond0.101
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brRLAN inet manual
     bridge_ports bond0.255
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brTEST inet manual
     bridge_ports bond0.200
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brBE inet manual
     bridge_ports bond0.70
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brFE inet manual
     bridge_ports bond0.201
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0
iface brDMZ0 inet manual
     bridge_ports enp4s0f0
     bridge_stp off
     bridge_waitport 0
     bridge_fd 0

### problem description

I have several domU on my Debian dom0. One of the domU is an opnsense
fw. Another one is
a storage driver domain serving zfs file system. All works so far so good.

Some time ago I experienced a complete restart of the dom0 after adding
new wifi devices
or using the Android app PingTools for scanning the local wifi net (the
dom0 has connectivity
to all local vlans).

I can reproduce the issue with all domU shut down so it is related to
the dom0.

 From the kernel panic it seems it is bnx2 related.

2 of The 4 bnx2 interfaces I am using ar configured as a bonding
interface. Will try to change
that to see if it is related to the bonding configuration.

Any help would be appreciated,
spi

[toc] | [next] | [standalone]

#72347

FromSebastian Piecha <sebastian@piecha.net>
Date2021-07-03 18:30 +0200
Message-ID<CwQGJ-6Bk-1@gated-at.bofh.it>
In reply to#72346
Without bonding 2 interfaces there is no kernel panic so far.

spi

[toc] | [prev] | [next] | [standalone]

#72357

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-07-05 15:00 +0200
Message-ID<CxwmB-7Qh-3@gated-at.bofh.it>
In reply to#72346
Control: tags -1 + moreinfo

On Sat, Jul 03, 2021 at 05:26:04PM +0200, spi@gmxpro.de wrote:
> Package: src:linux
> Version: 4.19.194-1
> Severity: important
> 
> 
> 
> -- Package-specific info:
> ** Version:
> Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc
> version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-1 (2021-06-10)
> 
> ** Command line:
> placeholder root=/dev/mapper/srvxen04-root ro console=ttyS0,115200n8
> console=tty0 intel_iommu=on nomodeset net.ifnames=1 biosdevname=0
> 
> ** Not tainted
> 
> ** Kernel log:
> [   39.592859] vif vif-1-0 vif-fw2-OAM: renamed from vif1.0
> [   39.620827] vif vif-1-3 vif-fw2-FE: renamed from vif1.3
> [   39.648849] vif vif-1-2 vif-fw2-DMZ0: renamed from vif1.2
> [   39.676964] vif vif-1-6 vif-fw2-TEST: renamed from vif1.6
> [   39.712828] vif vif-1-8 vif-fw2-HOME: renamed from vif1.8
> [   39.796755] brLAN: port 2(vif-fw2-LAN) entered blocking state
> [   39.802908] brLAN: port 2(vif-fw2-LAN) entered disabled state
> [   39.809479] device vif-fw2-LAN entered promiscuous mode
> [   39.815267] brOAM: port 2(vif-fw2-OAM) entered blocking state
> [   39.821493] brOAM: port 2(vif-fw2-OAM) entered disabled state
> [   39.827692] device vif-fw2-OAM entered promiscuous mode
> [   39.833365] brWLAN: port 2(vif-fw2-WLAN) entered blocking state
> [   39.839769] brWLAN: port 2(vif-fw2-WLAN) entered disabled state
> [   39.846161] device vif-fw2-WLAN entered promiscuous mode
> [   39.851967] brDMZ0: port 2(vif-fw2-DMZ0) entered blocking state
> [   39.858295] brDMZ0: port 2(vif-fw2-DMZ0) entered disabled state
> [   39.864659] device vif-fw2-DMZ0 entered promiscuous mode
> [   39.874675] brFE: port 2(vif-fw2-FE) entered blocking state
> [   39.880621] brFE: port 2(vif-fw2-FE) entered disabled state
> [   39.886968] device vif-fw2-FE entered promiscuous mode
> [   39.893906] brRLAN: port 2(vif-fw2-RLAN) entered blocking state
> [   39.900254] brRLAN: port 2(vif-fw2-RLAN) entered disabled state
> [   39.907304] device vif-fw2-RLAN entered promiscuous mode
> [   39.915348] brTEST: port 2(vif-fw2-TEST) entered blocking state
> [   39.921718] brTEST: port 2(vif-fw2-TEST) entered disabled state
> [   39.928290] device vif-fw2-TEST entered promiscuous mode
> [   39.934666] brBE: port 2(vif-fw2-BE) entered blocking state
> [   39.940616] brBE: port 2(vif-fw2-BE) entered disabled state
> [   39.946814] device vif-fw2-BE entered promiscuous mode
> [   39.953792] brHOME: port 2(vif-fw2-HOME) entered blocking state
> [   39.960107] brHOME: port 2(vif-fw2-HOME) entered disabled state
> [   39.966581] device vif-fw2-HOME entered promiscuous mode
> [   42.160336] xen-blkback: backend/vbd/1/51712: using 1 queues,
> protocol 1 (x86_64-abi)
> [   42.353338] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
> [   42.358612] brOAM: port 2(vif-fw2-OAM) entered blocking state
> [   42.364733] brOAM: port 2(vif-fw2-OAM) entered forwarding state
> [   42.378050] vif vif-1-1 vif-fw2-LAN: Guest Rx ready
> [   42.383309] brLAN: port 2(vif-fw2-LAN) entered blocking state
> [   42.389427] brLAN: port 2(vif-fw2-LAN) entered forwarding state
> [   42.428330] vif vif-1-2 vif-fw2-DMZ0: Guest Rx ready
> [   42.433682] brDMZ0: port 2(vif-fw2-DMZ0) entered blocking state
> [   42.440053] brDMZ0: port 2(vif-fw2-DMZ0) entered forwarding state
> [   42.448264] vif vif-1-3 vif-fw2-FE: Guest Rx ready
> [   42.453429] brFE: port 2(vif-fw2-FE) entered blocking state
> [   42.459409] brFE: port 2(vif-fw2-FE) entered forwarding state
> [   42.467498] vif vif-1-4 vif-fw2-BE: Guest Rx ready
> [   42.472669] brBE: port 2(vif-fw2-BE) entered blocking state
> [   42.478647] brBE: port 2(vif-fw2-BE) entered forwarding state
> [   42.486688] vif vif-1-5 vif-fw2-WLAN: Guest Rx ready
> [   42.492049] brWLAN: port 2(vif-fw2-WLAN) entered blocking state
> [   42.498370] brWLAN: port 2(vif-fw2-WLAN) entered forwarding state
> [   42.506575] vif vif-1-6 vif-fw2-TEST: Guest Rx ready
> [   42.511964] brTEST: port 2(vif-fw2-TEST) entered blocking state
> [   42.518364] brTEST: port 2(vif-fw2-TEST) entered forwarding state
> [   42.526458] vif vif-1-7 vif-fw2-RLAN: Guest Rx ready
> [   42.531790] brRLAN: port 2(vif-fw2-RLAN) entered blocking state
> [   42.538105] brRLAN: port 2(vif-fw2-RLAN) entered forwarding state
> [   42.546365] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
> [   42.551699] brHOME: port 2(vif-fw2-HOME) entered blocking state
> [   42.557990] brHOME: port 2(vif-fw2-HOME) entered forwarding state
> [   52.749924] brBE: port 2(vif-fw2-BE) entered disabled state
> [   52.857180] vif vif-1-4 vif-fw2-BE: Guest Rx ready
> [   52.862389] brBE: port 2(vif-fw2-BE) entered blocking state
> [   52.868356] brBE: port 2(vif-fw2-BE) entered forwarding state
> [   53.011574] vif vif-1-4 vif-fw2-BE: Guest Rx ready
> [   53.011597] NOHZ: local_softirq_pending 08
> [   53.145228] vif vif-1-3 vif-fw2-FE: Guest Rx ready
> [   53.253183] vif vif-1-3 vif-fw2-FE: Guest Rx ready
> [   53.253214] NOHZ: local_softirq_pending 08
> [   53.377074] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
> [   53.493773] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
> [   53.493792] NOHZ: local_softirq_pending 08
> [   53.648414] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
> [   53.761142] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
> [   53.761165] NOHZ: local_softirq_pending 08
> [   53.948967] vif vif-1-6 vif-fw2-TEST: Guest Rx ready
> [   54.059419] vif vif-1-6 vif-fw2-TEST: Guest Rx ready
> [   54.059437] NOHZ: local_softirq_pending 08
> [   54.197135] vif vif-1-1 vif-fw2-LAN: Guest Rx ready
> [   54.308315] vif vif-1-1 vif-fw2-LAN: Guest Rx ready
> [   54.308334] NOHZ: local_softirq_pending 08
> [   54.445602] vif vif-1-7 vif-fw2-RLAN: Guest Rx ready
> [   54.568490] vif vif-1-7 vif-fw2-RLAN: Guest Rx ready
> [   54.728865] vif vif-1-5 vif-fw2-WLAN: Guest Rx ready
> [   54.845130] vif vif-1-5 vif-fw2-WLAN: Guest Rx ready
> [   54.845150] NOHZ: local_softirq_pending 08
> [   74.929309] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
> MAC=ff:ff:ff:ff:ff:ff:c4:ad:34:93:14:ea:08:00 SRC=192.168.254.18
> DST=255.255.255.255 LEN=152 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
> SPT=5678 DPT=5678 LEN=132
> [   77.182871] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
> MAC=ff:ff:ff:ff:ff:ff:00:e0:4c:68:06:cd:08:00 SRC=192.168.254.194
> DST=192.168.254.255 LEN=569 TOS=0x00 PREC=0x00 TTL=64 ID=62930 DF
> PROTO=UDP SPT=51786 DPT=21027 LEN=549
> [   79.451615] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
> MAC=ff:ff:ff:ff:ff:ff:c4:ad:34:c0:a4:e4:08:00 SRC=192.168.254.19
> DST=255.255.255.255 LEN=151 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
> SPT=5678 DPT=5678 LEN=131
> [   83.328385] vif vif-2-0 vif-iam-BE: renamed from vif2.0
> [   83.396142] brBE: port 3(vif-iam-BE) entered blocking state
> [   83.402125] brBE: port 3(vif-iam-BE) entered disabled state
> [   83.408134] device vif-iam-BE entered promiscuous mode
> [   84.354072] xen-blkback: backend/vbd/2/51714: using 1 queues,
> protocol 1 (x86_64-abi) persistent grants
> [   84.370113] vif vif-2-0 vif-iam-BE: Guest Rx ready
> [   84.375381] brBE: port 3(vif-iam-BE) entered blocking state
> [   84.377168] xen-blkback: backend/vbd/2/51713: using 1 queues,
> protocol 1 (x86_64-abi) persistent grants
> [   84.381355] brBE: port 3(vif-iam-BE) entered forwarding state
> [   92.005330] iptables denied: IN=brOAM OUT= PHYSIN=enp4s0f1
> MAC=ff:ff:ff:ff:ff:ff:c4:ad:34:90:19:a4:08:00 SRC=192.168.254.16
> DST=255.255.255.255 LEN=152 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
> SPT=5678 DPT=5678 LEN=132
> [   97.954330] iptables denied: IN=brTEST OUT= PHYSIN=bond0.200
> MAC=ff:ff:ff:ff:ff:ff:40:31:3c:a7:9b:57:08:00 SRC=0.0.0.0
> DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP
> SPT=68 DPT=67 LEN=308
> 
> ** Model information
> sys_vendor: System manufacturer
> product_name: System Product Name
> product_version: System Version
> chassis_vendor: Chassis Manufacture
> chassis_version: Chassis Version
> bios_vendor: American Megatrends Inc.
> bios_version: 1302
> board_vendor: ASUSTeK COMPUTER INC.
> board_name: P8Q77-M
> board_version: Rev X.0x
> 
> ** Loaded modules:
> xen_netback
> xen_blkback
> 8021q
> garp
> mrp
> bonding
> nf_log_ipv6
> xen_gntdev
> ip6t_REJECT
> nf_reject_ipv6
> xen_evtchn
> xenfs
> xen_privcmd
> br_netfilter
> bridge
> stp
> llc
> nf_log_ipv4
> nf_log_common
> nft_limit
> nft_counter
> dm_snapshot
> dm_bufio
> xt_physdev
> xt_LOG
> xt_limit
> xt_tcpudp
> xt_state
> xt_conntrack
> nf_conntrack
> nf_defrag_ipv6
> nf_defrag_ipv4
> ipt_REJECT
> nf_reject_ipv4
> nft_compat
> nf_tables
> nfnetlink
> intel_powerclamp
> crct10dif_pclmul
> crc32_pclmul
> ghash_clmulni_intel
> mei_wdt
> eeepc_wmi
> asus_wmi
> sparse_keymap
> rfkill
> wmi_bmof
> pcspkr
> iTCO_wdt
> iTCO_vendor_support
> evdev
> joydev
> mei_me
> mei
> i915
> drm_kms_helper
> drm
> i2c_algo_bit
> sg
> wmi
> video
> button
> xen_pciback
> loop
> sunrpc
> ip_tables
> x_tables
> autofs4
> ext4
> crc16
> mbcache
> jbd2
> fscrypto
> ecb
> dm_mod
> raid10
> raid456
> async_raid6_recov
> async_memcpy
> async_pq
> async_xor
> async_tx
> xor
> raid6_pq
> libcrc32c
> crc32c_generic
> raid1
> raid0
> multipath
> linear
> md_mod
> sd_mod
> hid_generic
> usbhid
> hid
> crc32c_intel
> ahci
> aesni_intel
> aes_x86_64
> libahci
> crypto_simd
> cryptd
> glue_helper
> xhci_pci
> libata
> i2c_i801
> lpc_ich
> ehci_pci
> mfd_core
> mpt3sas
> raid_class
> ehci_hcd
> xhci_hcd
> scsi_transport_sas
> scsi_mod
> bnx2
> usbcore
> e1000e
> usb_common
> thermal
> fan
> 
> ** Network interface configuration:
> 
> -- System Information:
> Debian Release: 10.10
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages linux-image-4.19.0-17-amd64 depends on:
> ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
> ii  kmod                                    26-1
> ii  linux-base                              4.6
> 
> Versions of packages linux-image-4.19.0-17-amd64 recommends:
> ii  apparmor             2.13.2-10
> ii  firmware-linux-free  3.4
> 
> Versions of packages linux-image-4.19.0-17-amd64 suggests:
> pn  debian-kernel-handbook  <none>
> ii  grub-pc                 2.02+dfsg1-20+deb10u4
> ii  linux-doc-4.19          4.19.194-1
> 
> Versions of packages linux-image-4.19.0-17-amd64 is related to:
> pn  firmware-amd-graphics                       <none>
> pn  firmware-atheros                            <none>
> ii  firmware-bnx2                               20190114-2
> pn  firmware-bnx2x                              <none>
> pn  firmware-brcm80211                          <none>
> pn  firmware-cavium                             <none>
> pn  firmware-intel-sound                        <none>
> pn  firmware-intelwimax                         <none>
> pn  firmware-ipw2x00                            <none>
> pn  firmware-ivtv                               <none>
> pn  firmware-iwlwifi                            <none>
> pn  firmware-libertas                           <none>
> pn  firmware-linux-nonfree                      <none>
> pn  firmware-misc-nonfree                       <none>
> pn  firmware-myricom                            <none>
> pn  firmware-netxen                             <none>
> pn  firmware-qlogic                             <none>
> pn  firmware-realtek                            <none>
> pn  firmware-samsung                            <none>
> pn  firmware-siano                              <none>
> pn  firmware-ti-connectivity                    <none>
> ii  xen-hypervisor-4.11-amd64 [xen-hypervisor] 4.11.4+107-gef32c7afa2-1
> 
> -- no debconf information
> 
> ### Kernel Panic
> 
> [ 2659.446701] BUG: unable to handle kernel NULL pointer dereference at
> 0000000000000080
> [ 2659.540562] PGD 0 P4D 0
> [ 2659.570927] Oops: 0000 [#1] SMP NOPTI
> [ 2659.614816] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.0-17-amd64
> #1 Debian 4.19.194-1
> [ 2659.713823] Hardware name: System manufacturer System Product
> Name/P8Q77-M, BIOS 1302 08/06/2014
> [ 2659.819073] RIP: e030:bnx2_poll_work+0x61f/0x12c0 [bnx2]
> [ 2659.882716] Code: 10 48 89 d7 48 81 c7 a8 00 00 00 0f 84 fb 00 00 00
> 48 8b 92 b8 02 00 00 48 85 d2 0f 84 eb 00 00 00 4c 8b 4a 28 4d 85 c9 74
> 1f <41> 8b 97 80 00 00 00 48 8b 75 08 45 31 c0 b9 01 00 00 00 41 2b 97
> [ 2660.107569] RSP: e02b:ffff88803e603e08 EFLAGS: 00010286
> [ 2660.170170] RAX: ffff88803095e000 RBX: 0000000000005dba RCX:
> 000000000000022e
> [ 2660.255658] RDX: ffffffff81cc12e0 RSI: 9730aa88f5172c0a RDI:
> ffff888039b110a8
> [ 2660.341147] RBP: ffff88803095f170 R08: 00000000000271d0 R09:
> ffffffff814a7c90
> [ 2660.426636] R10: ffffea00002faa00 R11: 0000000000000000 R12:
> 0000000000000050
> [ 2660.512123] R13: ffff8880329f88c0 R14: ffff8880329f8d80 R15:
> 0000000000000000
> [ 2660.597617] FS:  00007fb65e0f0740(0000) GS:ffff88803e600000(0000)
> knlGS:0000000000000000
> [ 2660.694536] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 2660.763383] CR2: 0000000000000080 CR3: 0000000031fe2000 CR4:
> 0000000000040660
> [ 2660.848880] Call Trace:
> [ 2660.878204]  <IRQ>
> [ 2660.902339]  ? __napi_schedule+0x63/0x70
> [ 2660.949342]  bnx2_poll_msix+0x33/0xd0 [bnx2]
> [ 2661.000511]  net_rx_action+0x149/0x3b0
> [ 2661.045440]  __do_softirq+0xde/0x2d8
> [ 2661.088290]  irq_exit+0xba/0xc0
> [ 2661.125937]  xen_evtchn_do_upcall+0x2c/0x40
> [ 2661.176057]  xen_do_hypervisor_callback+0x29/0x40
> [ 2661.232422]  </IRQ>
> [ 2661.257587] RIP: e030:xen_hypercall_sched_op+0xa/0x20
> [ 2661.318116] Code: 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc
> cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f
> 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
> [ 2661.542969] RSP: e02b:ffffffff82003e70 EFLAGS: 00000246
> [ 2661.605569] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
> ffffffff810013aa
> [ 2661.691057] RDX: 00000000014282fa RSI: 0000000000000000 RDI:
> 0000000000000001
> [ 2661.776546] RBP: 0000000000000000 R08: 000000002d3bca96 R09:
> 0000000000000008
> [ 2661.862033] R10: 0000000000007ff0 R11: 0000000000000246 R12:
> 0000000000000000
> [ 2661.947519] R13: 0000000000000000 R14: 0000000000000000 R15:
> 0000000000000000
> [ 2662.033012]  ? xen_hypercall_sched_op+0xa/0x20
> [ 2662.086255]  ? xen_safe_halt+0xc/0x20
> [ 2662.130144]  ? default_idle+0x1c/0x140
> [ 2662.175070]  ? do_idle+0x1e3/0x270
> [ 2662.215839]  ? cpu_startup_entry+0x6f/0x80
> [ 2662.264927]  ? start_kernel+0x507/0x52a
> [ 2662.310893]  ? default_get_nmi_reason+0x10/0x10
> [ 2662.365181]  ? xen_start_kernel+0x5a4/0x5af
> [ 2662.415308] Modules linked in: xen_netback xen_blkback 8021q garp mrp
> bonding xen_gntdev nf_log_ipv6 ip6t_REJECT xen_evtchn nf_reject_ipv6
> xenfs xen_privcmd br_netfilter bridge stp llc nf_log_ipv4 nf_log_common
> nft_limit nft_counter xt_physdev xt_LOG xt_limit xt_tcpudp dm_snapshot
> xt_state dm_bufio xt_conntrack nf_conntrack nf_defrag_ipv6
> nf_defrag_ipv4 ipt_REJECT nf_reject_ipv4 nft_compat nf_tables nfnetlink
> intel_powerclamp crct10dif_pclmul crc32_pclmul eeepc_wmi asus_wmi
> ghash_clmulni_intel sparse_keymap mei_wdt rfkill wmi_bmof pcspkr
> iTCO_wdt i915 joydev evdev iTCO_vendor_support drm_kms_helper drm mei_me
> mei i2c_algo_bit sg wmi video button xen_pciback loop sunrpc ip_tables
> x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb dm_mod raid10
> raid456 async_raid6_recov async_memcpy async_pq async_xor
> [ 2663.266470]  async_tx xor raid6_pq libcrc32c crc32c_generic raid1
> raid0 multipath linear md_mod hid_generic usbhid hid sd_mod crc32c_intel
> aesni_intel ahci aes_x86_64 crypto_simd cryptd libahci glue_helper
> lpc_ich i2c_i801 ehci_pci libata mpt3sas xhci_pci mfd_core raid_class
> xhci_hcd ehci_hcd scsi_transport_sas e1000e bnx2 usbcore scsi_mod
> usb_common thermal fan
> [ 2663.650520] CR2: 0000000000000080
> [ 2663.691381] ---[ end trace 7a21ad49627256e7 ]---
> [ 2663.746711] RIP: e030:bnx2_poll_work+0x61f/0x12c0 [bnx2]
> [ 2663.810353] Code: 10 48 89 d7 48 81 c7 a8 00 00 00 0f 84 fb 00 00 00
> 48 8b 92 b8 02 00 00 48 85 d2 0f 84 eb 00 00 00 4c 8b 4a 28 4d 85 c9 74
> 1f <41> 8b 97 80 00 00 00 48 8b 75 08 45 31 c0 b9 01 00 00 00 41 2b 97
> [ 2664.035208] RSP: e02b:ffff88803e603e08 EFLAGS: 00010286
> [ 2664.097809] RAX: ffff88803095e000 RBX: 0000000000005dba RCX:
> 000000000000022e
> [ 2664.183298] RDX: ffffffff81cc12e0 RSI: 9730aa88f5172c0a RDI:
> ffff888039b110a8
> [ 2664.268782] RBP: ffff88803095f170 R08: 00000000000271d0 R09:
> ffffffff814a7c90
> [ 2664.354270] R10: ffffea00002faa00 R11: 0000000000000000 R12:
> 0000000000000050
> [ 2664.439759] R13: ffff8880329f88c0 R14: ffff8880329f8d80 R15:
> 0000000000000000
> [ 2664.525252] FS:  00007fb65e0f0740(0000) GS:ffff88803e600000(0000)
> knlGS:0000000000000000
> [ 2664.622175] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 2664.691021] CR2: 0000000000000080 CR3: 0000000031fe2000 CR4:
> 0000000000040660
> [ 2664.776512] Kernel panic - not syncing: Fatal exception in interrupt
> [ 2664.852642] Kernel Offset: disabled
> 
> 
> ### network controller
> 
> lspci | grep net
> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
> Connection (rev 04)
> 04:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
> Gigabit Ethernet (rev 20)
> 04:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
> Gigabit Ethernet (rev 20)
> 05:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
> Gigabit Ethernet (rev 20)
> 05:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
> Gigabit Ethernet (rev 20)
> 
> ### interface configuration
> 
> auto lo
> iface lo inet loopback
> auto enp4s0f0
> iface enp4s0f0 inet manual
> auto enp4s0f1
> iface enp4s0f1 inet manual
> auto enp5s0f0
> iface enp5s0f0 inet manual
> auto enp5s0f1
> iface enp5s0f1 inet manual
> auto bond0
> iface bond0 inet manual
>         up ifconfig bond0 0.0.0.0 up
>         slaves enp5s0f1 enp5s0f0
>         bond-mode 802.3ad
>         bond-miimon 100
>         bond-downdelay 200
>         bond-updelay 200
>         bond-lacp-rate fast
>         bond-xmit-hash-policy layer2+3
>         post-up ifconfig enp5s0f0 mtu 8996 && ifconfig enp5s0f1 mtu
> 8996 && ifconfig bond0 mtu 8996
> auto brINT
> iface brINT inet static
>     pre-up brctl addbr $IFACE
>     up ip link set $IFACE up
>     post-down brctl delbr $IFACE
>     down ip link set $IFACE down
>     hwaddress ether 00:16:3E:24:00:11
>     address 192.168.240.11
>     network 192.168.240.0
>     netmask 255.255.255.0
>     broadcast 192.168.240.255
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> auto brOAM
> auto brLAN
> iface bond0.50 inet manual
> auto brWLAN
> iface bond0.100 inet manual
> auto brHOME
> iface bond0.101 inet manual
> auto brRLAN
> iface bond0.255 inet manual
> auto brTEST
> iface bond0.200 inet manual
> auto brBE
> iface bond0.70 inet manual
> auto brFE
> iface bond0.201 inet manual
> auto brDMZ0
> iface enp4s0f0 inet manual
> iface brOAM inet static
>     address 192.168.254.11
>     network 192.168.254.0
>     netmask 255.255.255.0
>     broadcast 192.168.254.255
>     gateway 192.168.254.1
>     dns-nameservers 192.168.254.1
>     bridge_ports enp4s0f1
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brLAN inet manual
>     bridge_ports bond0.50
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brWLAN inet manual
>     bridge_ports bond0.100
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brHOME inet manual
>     bridge_ports bond0.101
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brRLAN inet manual
>     bridge_ports bond0.255
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brTEST inet manual
>     bridge_ports bond0.200
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brBE inet manual
>     bridge_ports bond0.70
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brFE inet manual
>     bridge_ports bond0.201
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> iface brDMZ0 inet manual
>     bridge_ports enp4s0f0
>     bridge_stp off
>     bridge_waitport 0
>     bridge_fd 0
> 
> ### problem description
> 
> I have several domU on my Debian dom0. One of the domU is an opnsense
> fw. Another one is
> a storage driver domain serving zfs file system. All works so far so good.
> 
> Some time ago I experienced a complete restart of the dom0 after adding
> new wifi devices
> or using the Android app PingTools for scanning the local wifi net (the
> dom0 has connectivity
> to all local vlans).
> 
> I can reproduce the issue with all domU shut down so it is related to
> the dom0.
> 
> From the kernel panic it seems it is bnx2 related.
> 
> 2 of The 4 bnx2 interfaces I am using ar configured as a bonding
> interface. Will try to change
> that to see if it is related to the bonding configuration.
> 
> Any help would be appreciated,
> spi

From the above description one thin is not fully clear to me, so
aksing specifically: Is this a regression introduced with the
4.19.194-1 upload or can you reproduce the issue earlier?

If a new regression introduced, can you possibly bisect to the
introducing commit?

Can you reproduce the issue with recent kernel from unstable or
buster-backports?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#72359

Fromspi@gmxpro.de
Date2021-07-05 15:10 +0200
Message-ID<Cxwwh-8as-1@gated-at.bofh.it>
In reply to#72357
>  From the above description one thin is not fully clear to me, so
> aksing specifically: Is this a regression introduced with the
> 4.19.194-1 upload or can you reproduce the issue earlier?
>

I had no spontaneous reboots within the last years so yes, the issue
seems to got introduced with one of the recent kernels in the last few
months.

> If a new regression introduced, can you possibly bisect to the
> introducing commit?
>
> Can you reproduce the issue with recent kernel from unstable or
> buster-backports?
>

I'm going to try a more recent kernel from backports or unstable to see
if issue still persist. As I this issue only pops up while using bonding
interfaces on a multiport GBE NIC I wonder if there is "just" a
configuration issue with the bonding interfaces.

Cheers
spi

[toc] | [prev] | [next] | [standalone]

#72370

Fromspi@gmxpro.de
Date2021-07-10 19:00 +0200
Message-ID<CzouB-3vL-1@gated-at.bofh.it>
In reply to#72357
>
> Can you reproduce the issue with recent kernel from unstable or
> buster-backports?
>

Tried with linux-image-5.10.0-0.bpo.7-amd64 (5.10.40-1~bpo10+1 amd64)
from buster-backports.

Same issue - kernel panic with bonded interfaces.

Current workaround for me is to run without bonding.

Cheers,
spi

[toc] | [prev] | [next] | [standalone]

#72373

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-07-10 22:00 +0200
Message-ID<CzriO-5hg-1@gated-at.bofh.it>
In reply to#72370
Control: found -1 5.10.40-1

Hi,

On Sat, Jul 10, 2021 at 06:40:08PM +0200, spi@gmxpro.de wrote:
> 
> > 
> > Can you reproduce the issue with recent kernel from unstable or
> > buster-backports?
> > 
> 
> Tried with linux-image-5.10.0-0.bpo.7-amd64 (5.10.40-1~bpo10+1 amd64)
> from buster-backports.
> 
> Same issue - kernel panic with bonded interfaces.
> 
> Current workaround for me is to run without bonding.

thanks for confirming this as well, so adding a found version. Next
step would be to check the latest 5.10.y upstream version. If it's an
issue there, next to report it upstream.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#72380

Fromspi@gmxpro.de
Date2021-07-13 15:30 +0200
Message-ID<CAqE1-23D-7@gated-at.bofh.it>
In reply to#72373
>
> thanks for confirming this as well, so adding a found version. Next
> step would be to check the latest 5.10.y upstream version. If it's an
> issue there, next to report it upstream.
>

Just to understand that correctly - shall I wait for the next update for
the kernel in buster-backports and try that one?

I tried 5.10.40-1~bpo10+1 amd64 which is currently the latest one in
buster-backports.

spi

[toc] | [prev] | [next] | [standalone]

#72383

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-07-14 11:30 +0200
Message-ID<CAJnj-60i-1@gated-at.bofh.it>
In reply to#72380
Hi,

On Tue, Jul 13, 2021 at 03:26:22PM +0200, spi@gmxpro.de wrote:
>
> >
> > thanks for confirming this as well, so adding a found version. Next
> > step would be to check the latest 5.10.y upstream version. If it's an
> > issue there, next to report it upstream.
> >
>
> Just to understand that correctly - shall I wait for the next update for
> the kernel in buster-backports and try that one?
>
> I tried 5.10.40-1~bpo10+1 amd64 which is currently the latest one in
> buster-backports.

Actually I was targetting at something else (but apart that if you can
fetch the unstable's kernel then you can verify as well 5.10.46-1): I
meant to verify directly upstream's mainline and latest 5.10.y form
upstream.

How to do that, we tried to document in
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-kernel-org-package 

If you find the issue is still present in the most current version, my
aim was that we can report it upstream as issue.

One further aspect is: If you find an earlier version you known to be
non-broken with the setup, bisecting could lead to the introducing
commit which introduces the issue, and so enlight some further more.

Does this help so far?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#72384

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-07-14 11:40 +0200
Message-ID<CAJx0-63v-9@gated-at.bofh.it>
In reply to#72380
One thing I forgot to ask in the previous message: you have 4
interfaces: did you check if you trigger the issue if you change
the two interfaces you want to bond? Just to double-check.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#72391

Fromspi@gmxpro.de
Date2021-07-17 20:40 +0200
Message-ID<CBXoe-3Vq-11@gated-at.bofh.it>
In reply to#72384
So, did some more testing.

1) Tried two different ports for binding interface on the 4-port-NIC:
again kernel panic

2) Compiled mainline 5.14-rc1 (2021-07-11) kernel from kernel.org: again
kernel panic with either two ports on the 4-port-NIC


3) Added another 2-port-NIC into server:
06:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
Controller (Copper) (rev 03)

06:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
Controller (Copper) (rev 03)

driver: e1000
version: 7.3.21-k8-NAPI


When configuring a two port bonding interface on this Intel NIC there is
no kernel panic neither with 5.14-rc1 nor 4.19.0-17-amd64.


For me it seems there is an issue with the bnx2 driver used for the
Broadcom Limited NetXtreme II BCM5709 Gigabit Ethernet (rev 20).

Cheers,
spi

[toc] | [prev] | [next] | [standalone]

#72518

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-07-29 23:10 +0200
Message-ID<CGlrX-3OS-1@gated-at.bofh.it>
In reply to#72391
Hi,

On Sat, Jul 17, 2021 at 08:32:42PM +0200, spi@gmxpro.de wrote:
> 
> So, did some more testing.
> 
> 1) Tried two different ports for binding interface on the 4-port-NIC:
> again kernel panic
> 
> 2) Compiled mainline 5.14-rc1 (2021-07-11) kernel from kernel.org: again
> kernel panic with either two ports on the 4-port-NIC
> 
> 
> 3) Added another 2-port-NIC into server:
> 06:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
> Controller (Copper) (rev 03)
> 
> 06:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
> Controller (Copper) (rev 03)
> 
> driver: e1000
> version: 7.3.21-k8-NAPI
> 
> 
> When configuring a two port bonding interface on this Intel NIC there is
> no kernel panic neither with 5.14-rc1 nor 4.19.0-17-amd64.
> 
> 
> For me it seems there is an issue with the bnx2 driver used for the
> Broadcom Limited NetXtreme II BCM5709 Gigabit Ethernet (rev 20).

So sorry to not coming back to this earlier. Now that you were able to
reproduce the very same with mainline, can you report the issue to
upstream? cripts/get_maintainer.pl would suggst the following:

Rasesh Mody <rmody@marvell.com> (supporter:BROADCOM BNX2 GIGABIT ETHERNET DRIVER)
GR-Linux-NIC-Dev@marvell.com (supporter:BROADCOM BNX2 GIGABIT ETHERNET DRIVER)
"David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING DRIVERS)
Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING DRIVERS)
Ariel Elior <aelior@marvell.com> (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER)
Sudarsana Kalluru <skalluru@marvell.com> (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER)
GR-everest-linux-l2@marvell.com (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER)
netdev@vger.kernel.org (open list:BROADCOM BNX2 GIGABIT ETHERNET DRIVER)
linux-kernel@vger.kernel.org (open list)

Please keep ideally directly the Debian bug ideally in the loop.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#72562

Fromspi@gmxpro.de
Date2021-08-05 14:10 +0200
Message-ID<CIKme-37N-1@gated-at.bofh.it>
In reply to#72518
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.

Cheers,
spi

[toc] | [prev] | [next] | [standalone]

#73135

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-09-30 17:10 +0200
Message-ID<D35R8-14B-9@gated-at.bofh.it>
In reply to#72562
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

[toc] | [prev] | [next] | [standalone]

#73231

Fromspi@gmxpro.de
Date2021-10-09 13:30 +0200
Message-ID<D6iIi-6Yq-121@gated-at.bofh.it>
In reply to#73135
>
> Did you got any response on your reporting upstream?
>
No, not yet. Troubleshooting took quite some time and in the meantime
there is a new upstream kernel version available. So I need to rerun all
tests again. As this is a productive server I can only shutdown the
server every now and then on weekends.

Cheers,
Sebastian

[toc] | [prev] | [next] | [standalone]

#73138

FromHans van Kranenburg <hans@knorrie.org>
Date2021-09-30 22:20 +0200
Message-ID<D3aH8-3Xq-15@gated-at.bofh.it>
In reply to#72562
Hi spi, Salvatore,

On 8/5/21 1:58 PM, 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)

Just FWIW, I'm seeing this bug-mail-thread now, and it rings a bell.

I spent some time in the past to debug crashing BCM5719 (4x1G) nics in
HP DL360 G8/9 series servers. In this case, the firmware inside the nic
crashed, so the symptoms were different. This happened only when having
a Xen domU active as router, which was routing incoming traffic packets
(from outside the box) back to the outside again.

02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
Ethernet PCIe (rev 01)
02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
Ethernet PCIe (rev 01)
02:00.2 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
Ethernet PCIe (rev 01)
02:00.3 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
Ethernet PCIe (rev 01)

Also, 2x 1G were bonded, I use openvswitch with LACP for that.

The symptoms are obviously different, mine looked like this:

tg3 0000:02:00.2 eth1: transmit timed out, resetting
tg3 0000:02:00.2 eth1: 0x00000000: 0x165714e4, 0x00100546, 0x02000001,
0x00800010
tg3 0000:02:00.2 eth1: 0x00000010: 0x92b3000c, 0x00000000, 0x92b4000c,
0x00000000
tg3 0000:02:00.2 eth1: 0x00000020: 0x92b5000c, 0x00000000, 0x00000000,
0x22be103c

tg3 0000:02:00.2 eth1: 0x00007000: 0x08000008, 0x00000000, 0x00000000,
0x00004cd8
tg3 0000:02:00.2 eth1: 0x00007010: 0xdbbd2b97, 0x010080f3, 0x00d70081,
0x03008200
tg3 0000:02:00.2 eth1: 0x00007020: 0x00000000, 0x00000000, 0x00000406,
0x10004000
tg3 0000:02:00.2 eth1: 0x00007030: 0x00020000, 0x00004cdc, 0x001f0000,
0x00000000
tg3 0000:02:00.2 eth1: 0: Host status block
[00000001:00000070:(0000:0563:0000):(0000:0094)]
tg3 0000:02:00.2 eth1: 0: NAPI info
[00000070:00000070:(016a:0094:01ff):0000:(068c:0000:0000:0000)]
tg3 0000:02:00.2 eth1: 1: Host status block
[00000001:00000083:(0000:0000:0000):(015b:0000)]
tg3 0000:02:00.2 eth1: 1: NAPI info
[00000051:00000051:(0000:0000:01ff):0124:(0124:0124:0000:0000)]
tg3 0000:02:00.2 eth1: 2: Host status block
[00000001:000000d8:(0e96:0000:0000):(0000:0000)]
tg3 0000:02:00.2 eth1: 2: NAPI info
[000000a4:000000a4:(0000:0000:01ff):0e5b:(065b:065b:0000:0000)]
tg3 0000:02:00.2 eth1: 3: Host status block
[00000001:00000013:(0000:0000:0000):(0000:0000)]
tg3 0000:02:00.2 eth1: 3: NAPI info
[000000f8:000000f8:(0000:0000:01ff):072f:(072f:072f:0000:0000)]
tg3 0000:02:00.2 eth1: 4: Host status block
[00000001:0000009c:(0000:0000:0736):(0000:0000)]
tg3 0000:02:00.2 eth1: 4: NAPI info
[0000007c:0000007c:(0000:0000:01ff):0716:(0716:0716:0000:0000)]
tg3 0000:02:00.2: tg3_stop_block timed out, ofs=1400 enable_bit=2
tg3 0000:02:00.2: tg3_stop_block timed out, ofs=c00 enable_bit=2
tg3 0000:02:00.2 eth1: Link is down
tg3 0000:02:00.2 eth1: Link is up at 1000 Mbps, full duplex
tg3 0000:02:00.2 eth1: Flow control is off for TX and off for RX
tg3 0000:02:00.2 eth1: EEE is disabled

> - sysctl parameter net.bridge.bridge-nf-call-ip6tables is set to 0.
> 
> If both conditions are not met no kernel panic oaccurs.

What I found out in the end is that using `ethtool -K $iface tso off` is
a workaround to not make it trigger some obscure bug inside the nic that
makes it crash.

So, I think my actual suggestion would be, even while it does not look
like the same thing, but it's still Broadcom stuff which can have
*cough* weird issues... if you can reliably reproduce the problem, then
can you try setting tso off on the physical interfaces in dom0 and try
again? In Dutch we say "nooit geschoten altijd mis".

> 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.
> 
> Cheers,
> spi
> 

Have fun,
Hans

[toc] | [prev] | [next] | [standalone]

#73232

Fromspi@gmxpro.de
Date2021-10-09 13:40 +0200
Message-ID<D6iRP-71p-1@gated-at.bofh.it>
In reply to#73138
Am 30.09.21 um 22:03 schrieb Hans van Kranenburg:
> Hi spi, Salvatore,
>
> On 8/5/21 1:58 PM, 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)
>
> Just FWIW, I'm seeing this bug-mail-thread now, and it rings a bell.
>
> I spent some time in the past to debug crashing BCM5719 (4x1G) nics in
> HP DL360 G8/9 series servers. In this case, the firmware inside the nic
> crashed, so the symptoms were different. This happened only when having
> a Xen domU active as router, which was routing incoming traffic packets
> (from outside the box) back to the outside again.
>
> 02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
> Ethernet PCIe (rev 01)
> 02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
> Ethernet PCIe (rev 01)
> 02:00.2 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
> Ethernet PCIe (rev 01)
> 02:00.3 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit
> Ethernet PCIe (rev 01)
>
> Also, 2x 1G were bonded, I use openvswitch with LACP for that.
>
> The symptoms are obviously different, mine looked like this:
>
> tg3 0000:02:00.2 eth1: transmit timed out, resetting
> tg3 0000:02:00.2 eth1: 0x00000000: 0x165714e4, 0x00100546, 0x02000001,
> 0x00800010
> tg3 0000:02:00.2 eth1: 0x00000010: 0x92b3000c, 0x00000000, 0x92b4000c,
> 0x00000000
> tg3 0000:02:00.2 eth1: 0x00000020: 0x92b5000c, 0x00000000, 0x00000000,
> 0x22be103c
>
> tg3 0000:02:00.2 eth1: 0x00007000: 0x08000008, 0x00000000, 0x00000000,
> 0x00004cd8
> tg3 0000:02:00.2 eth1: 0x00007010: 0xdbbd2b97, 0x010080f3, 0x00d70081,
> 0x03008200
> tg3 0000:02:00.2 eth1: 0x00007020: 0x00000000, 0x00000000, 0x00000406,
> 0x10004000
> tg3 0000:02:00.2 eth1: 0x00007030: 0x00020000, 0x00004cdc, 0x001f0000,
> 0x00000000
> tg3 0000:02:00.2 eth1: 0: Host status block
> [00000001:00000070:(0000:0563:0000):(0000:0094)]
> tg3 0000:02:00.2 eth1: 0: NAPI info
> [00000070:00000070:(016a:0094:01ff):0000:(068c:0000:0000:0000)]
> tg3 0000:02:00.2 eth1: 1: Host status block
> [00000001:00000083:(0000:0000:0000):(015b:0000)]
> tg3 0000:02:00.2 eth1: 1: NAPI info
> [00000051:00000051:(0000:0000:01ff):0124:(0124:0124:0000:0000)]
> tg3 0000:02:00.2 eth1: 2: Host status block
> [00000001:000000d8:(0e96:0000:0000):(0000:0000)]
> tg3 0000:02:00.2 eth1: 2: NAPI info
> [000000a4:000000a4:(0000:0000:01ff):0e5b:(065b:065b:0000:0000)]
> tg3 0000:02:00.2 eth1: 3: Host status block
> [00000001:00000013:(0000:0000:0000):(0000:0000)]
> tg3 0000:02:00.2 eth1: 3: NAPI info
> [000000f8:000000f8:(0000:0000:01ff):072f:(072f:072f:0000:0000)]
> tg3 0000:02:00.2 eth1: 4: Host status block
> [00000001:0000009c:(0000:0000:0736):(0000:0000)]
> tg3 0000:02:00.2 eth1: 4: NAPI info
> [0000007c:0000007c:(0000:0000:01ff):0716:(0716:0716:0000:0000)]
> tg3 0000:02:00.2: tg3_stop_block timed out, ofs=1400 enable_bit=2
> tg3 0000:02:00.2: tg3_stop_block timed out, ofs=c00 enable_bit=2
> tg3 0000:02:00.2 eth1: Link is down
> tg3 0000:02:00.2 eth1: Link is up at 1000 Mbps, full duplex
> tg3 0000:02:00.2 eth1: Flow control is off for TX and off for RX
> tg3 0000:02:00.2 eth1: EEE is disabled
>
>> - sysctl parameter net.bridge.bridge-nf-call-ip6tables is set to 0.
>>
>> If both conditions are not met no kernel panic oaccurs.
>
> What I found out in the end is that using `ethtool -K $iface tso off` is
> a workaround to not make it trigger some obscure bug inside the nic that
> makes it crash.
>
> So, I think my actual suggestion would be, even while it does not look
> like the same thing, but it's still Broadcom stuff which can have
> *cough* weird issues... if you can reliably reproduce the problem, then
> can you try setting tso off on the physical interfaces in dom0 and try
> again? In Dutch we say "nooit geschoten altijd mis".
>

The next time I do maintenance I'll rerun the tests and set "ethtool -K
$iface tso off". "ethtool -K ${int} tx off" is alreday configured on the
server and I also tried tso off and others as well but didn't pay
attention to this bug at that time - as said the kernel panic doesn't
occur immediately but only after some minutes.

In German it is "wer nicht wagt, der nicht gewinnt" ;-)

>> 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 ***
>>

Do you recall what your setting for net.bridge.bridge-nf-call-ip6tables was?

>>
>> 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.
>>
>> Cheers,
>> spi
>>
>
> Have fun,
> Hans
>
Cheers,
Sebastian

[toc] | [prev] | [next] | [standalone]

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

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2021-07-05 15:00 +0200
SubjectProcessed: Re: Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709
Message-ID<CxwmC-7Qh-5@gated-at.bofh.it>
In reply to#72346
Processing control commands:

> tags -1 + moreinfo
Bug #990642 [src:linux] linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709
Added tag(s) moreinfo.

-- 
990642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

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

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2021-07-10 22:00 +0200
SubjectProcessed: Re: Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709
Message-ID<CzriO-5hg-3@gated-at.bofh.it>
In reply to#72346
Processing control commands:

> found -1 5.10.40-1
Bug #990642 [src:linux] linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709
Ignoring request to alter found versions of bug #990642 to the same values previously set

-- 
990642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web