Hello,
since upgrading to Kernel 5.15.35 I have following warning (and a second similar one) during boot:
The trace happens after initialising the network interfaces and bringing up vmbr0. No problems with former Kernel 5.13.19.
As stated, it is only a warning and the system is stable so far. Same behaviour on a different hardware in the cluster.
Any ideas what's missing here? Thank you for your support.
Dirk
since upgrading to Kernel 5.15.35 I have following warning (and a second similar one) during boot:
Code:
May 15 17:04:57 pve-2 kernel: WARNING: CPU: 0 PID: 1228 at include/net/netfilter/nf_conntrack.h:175 __ovs_ct_lookup+0x907/0xa40 [openvswitch]
May 15 17:04:57 pve-2 kernel: Modules linked in: bonding tls openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 softdog nfnetlink_log nfnetlink snd_hda_codec_hdmi snd_hda_c>
May 15 17:04:57 pve-2 kernel: sunrpc ip_tables x_tables autofs4 hid_generic usbmouse usbkbd usbhid hid zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blak>
May 15 17:04:57 pve-2 kernel: CPU: 0 PID: 1228 Comm: ovs-vswitchd Tainted: P C O 5.15.35-1-pve #1
May 15 17:04:57 pve-2 kernel: Hardware name: Supermicro Super Server/X11SBA-F, BIOS 1.1d 07/07/2020
May 15 17:04:57 pve-2 kernel: RIP: 0010:__ovs_ct_lookup+0x907/0xa40 [openvswitch]
May 15 17:04:57 pve-2 kernel: Code: 00 49 8b 94 24 c0 00 00 00 44 0f b6 3c 02 41 83 e7 0f 41 c1 e7 02 e9 69 fc ff ff 66 90 0f b6 53 1a 4c 8b 73 10 e9 59 f7 ff ff <0f> 0b e9 90 f7 ff ff 4c 89 d7 4c 89 >
May 15 17:04:57 pve-2 kernel: RSP: 0018:ffffadd7808875b0 EFLAGS: 00010246
May 15 17:04:57 pve-2 kernel: RAX: 0000000000000000 RBX: ffff9097c4042e20 RCX: 0000000000000000
May 15 17:04:57 pve-2 kernel: RDX: 0000000000000002 RSI: ffffadd7808875d0 RDI: 0000000000000000
May 15 17:04:57 pve-2 kernel: RBP: ffffadd780887680 R08: 0000000000000000 R09: ffffffff8f1b6cc0
May 15 17:04:57 pve-2 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff9097d5f9a100
May 15 17:04:57 pve-2 kernel: R13: ffff9097ca47eee8 R14: ffff9097c4042700 R15: 0000000000000000
May 15 17:04:57 pve-2 kernel: FS: 00007f066beeba40(0000) GS:ffff909937c00000(0000) knlGS:0000000000000000
May 15 17:04:57 pve-2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 15 17:04:57 pve-2 kernel: CR2: 00007ffe64fe9fd8 CR3: 000000010850a000 CR4: 00000000001006f0
May 15 17:04:57 pve-2 kernel: Call Trace:
May 15 17:04:57 pve-2 kernel: <TASK>
May 15 17:04:57 pve-2 kernel: ? nf_ct_get_tuple+0x13f/0x1e0 [nf_conntrack]
May 15 17:04:57 pve-2 kernel: ? nf_ct_get_tuplepr+0x64/0xa0 [nf_conntrack]
May 15 17:04:57 pve-2 kernel: ovs_ct_execute+0x449/0x8d0 [openvswitch]
May 15 17:04:57 pve-2 kernel: do_execute_actions+0xd4/0x1ab0 [openvswitch]
May 15 17:04:57 pve-2 kernel: ? call_rcu+0xa8/0x280
May 15 17:04:57 pve-2 kernel: ? __ovs_nla_copy_actions+0x979/0xf80 [openvswitch]
May 15 17:04:57 pve-2 kernel: ? __kmalloc_node_track_caller+0x16f/0x3a0
May 15 17:04:57 pve-2 kernel: ? __kmalloc+0x179/0x330
May 15 17:04:57 pve-2 kernel: ovs_execute_actions+0x48/0x110 [openvswitch]
May 15 17:04:57 pve-2 kernel: ? ovs_execute_actions+0x48/0x110 [openvswitch]
May 15 17:04:57 pve-2 kernel: ovs_packet_cmd_execute+0x280/0x300 [openvswitch]
May 15 17:04:57 pve-2 kernel: genl_family_rcv_msg_doit+0xe7/0x150
May 15 17:04:57 pve-2 kernel: genl_rcv_msg+0xe2/0x1e0
May 15 17:04:57 pve-2 kernel: ? ovs_vport_cmd_del+0x200/0x200 [openvswitch]
May 15 17:04:57 pve-2 kernel: ? genl_get_cmd+0xd0/0xd0
May 15 17:04:57 pve-2 kernel: netlink_rcv_skb+0x55/0x100
May 15 17:04:57 pve-2 kernel: genl_rcv+0x29/0x40
May 15 17:04:57 pve-2 kernel: netlink_unicast+0x221/0x330
May 15 17:04:57 pve-2 kernel: netlink_sendmsg+0x23f/0x4a0
May 15 17:04:57 pve-2 kernel: sock_sendmsg+0x65/0x70
May 15 17:04:57 pve-2 kernel: ____sys_sendmsg+0x257/0x2a0
May 15 17:04:57 pve-2 kernel: ? import_iovec+0x31/0x40
May 15 17:04:57 pve-2 kernel: ? sendmsg_copy_msghdr+0x7e/0xa0
May 15 17:04:57 pve-2 kernel: ? __check_object_size+0x4d/0x150
May 15 17:04:57 pve-2 kernel: ? _copy_from_user+0x2e/0x60
May 15 17:04:57 pve-2 kernel: ___sys_sendmsg+0x82/0xc0
May 15 17:04:57 pve-2 kernel: ? ___sys_recvmsg+0xa3/0x130
May 15 17:04:57 pve-2 kernel: ? __fget_files+0x86/0xc0
May 15 17:04:57 pve-2 kernel: ? __fget_light+0x32/0x80
May 15 17:04:57 pve-2 kernel: __sys_sendmsg+0x62/0xb0
May 15 17:04:57 pve-2 kernel: __x64_sys_sendmsg+0x1f/0x30
May 15 17:04:57 pve-2 kernel: do_syscall_64+0x5c/0xc0
May 15 17:04:57 pve-2 kernel: ? do_syscall_64+0x69/0xc0
May 15 17:04:57 pve-2 kernel: ? syscall_exit_to_user_mode+0x27/0x50
May 15 17:04:57 pve-2 kernel: ? __x64_sys_sendmsg+0x1f/0x30
May 15 17:04:57 pve-2 kernel: ? do_syscall_64+0x69/0xc0
May 15 17:04:57 pve-2 kernel: ? syscall_exit_to_user_mode+0x27/0x50
May 15 17:04:57 pve-2 kernel: ? __x64_sys_recvmsg+0x1f/0x30
May 15 17:04:57 pve-2 kernel: ? do_syscall_64+0x69/0xc0
May 15 17:04:57 pve-2 kernel: ? sysvec_apic_timer_interrupt+0x4e/0x90
May 15 17:04:57 pve-2 kernel: ? asm_sysvec_apic_timer_interrupt+0xa/0x20
May 15 17:04:57 pve-2 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
May 15 17:04:57 pve-2 kernel: RIP: 0033:0x7f066c817e4d
May 15 17:04:57 pve-2 kernel: Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 ca ee ff ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 >
May 15 17:04:57 pve-2 kernel: RSP: 002b:00007ffe64ffab20 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
May 15 17:04:57 pve-2 kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f066c817e4d
May 15 17:04:57 pve-2 kernel: RDX: 0000000000000000 RSI: 00007ffe64ffabb0 RDI: 0000000000000015
May 15 17:04:57 pve-2 kernel: RBP: 00007ffe64ffb9a0 R08: 0000000000000000 R09: 0000000000000001
May 15 17:04:57 pve-2 kernel: R10: 0000000000000004 R11: 0000000000000293 R12: 0000560fe267e2b0
May 15 17:04:57 pve-2 kernel: R13: 0000000000000000 R14: 0000560fe267e2b0 R15: 00007ffe64ffabb0
May 15 17:04:57 pve-2 kernel: </TASK>
May 15 17:04:57 pve-2 kernel: ---[ end trace 007b3b535cde2d0b ]---
The trace happens after initialising the network interfaces and bringing up vmbr0. No problems with former Kernel 5.13.19.
As stated, it is only a warning and the system is stable so far. Same behaviour on a different hardware in the cluster.
Any ideas what's missing here? Thank you for your support.
Dirk