Container neustart führt zum CPU stuck

N

nightcore

Renowned Member
Dec 2, 2015
6
1
68
Hi,
Ich fasse mal kurz mein setup zusammen. Auf meinem Host läuft aktuell Debian 8.10 mit Proxmox Version 4.4-22/2728f613 und dem PVE kernel 4.4.114-108.

Auf dem host habe ich eine IPv6 route zu einer meiner container eingerichtet. In diesem Container betreibe ich derzeit accel-ppp in einer l2tp/ipsec konfiguration. Die clienten im tunnel erhalten alle eine IPv6 aus einem kleinen 122 subnet. (Öffentliche IPs) Im container richte ich für jede vergebene IPv6 Adresse einen Neighbor Discovery Proxy ein. Beispielsweise:
ip neigh add proxy 2001:41d0:3:ed13:1ccd:a2bb:f18b:10 dev eth0

Das ganze funktioniert auch super. Sobald allerdings ein einziger Neighbor Discovery Proxy hinzugefügt wurde und auch der client über den tunnel verbunden ist und der container nun heruntergefahren wird kommt es zur vollständigen auslastungen eines CPU kerns und der load average geht an die decke.
Der komplette host reagiert danach überhaupt nicht mehr.
Der Kernel spuckt dabei folgendes aus:

Mar 28 22:15:08 jane pvedaemon[1865]: <root@pam> starting task UPID:jane:000057D2:0000D7D3:5ABBF7CC:vzshutdown:106:root@pam:
Mar 28 22:16:29 jane kernel: [ 634.115013] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:306 dev_watchdog+0x22e/0x240()
Mar 28 22:16:29 jane kernel: [ 634.125229] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 4.4.114-1-pve #1
Mar 28 22:16:29 jane kernel: [ 634.126805] 0000000000000286 acb48b767558c006 ffff88081f203da0 ffffffff81402343
Mar 28 22:16:29 jane kernel: [ 634.128318] 0000000000000000 ffff8807f606e280 0000000000000000 ffff8807f5a90000
Mar 28 22:16:29 jane kernel: [ 634.130512] [<ffffffff81083546>] warn_slowpath_common+0x86/0xc0
Mar 28 22:16:29 jane kernel: [ 634.133286] [<ffffffff810ef997>] call_timer_fn+0x37/0x140
Mar 28 22:16:29 jane kernel: [ 634.136083] [<ffffffff8108840e>] irq_exit+0x8e/0x90
Mar 28 22:16:29 jane kernel: [ 634.138809] [<ffffffff816eeb57>] cpuidle_enter+0x17/0x20
Mar 28 22:16:29 jane kernel: [ 634.141521] [<ffffffff818679ac>] rest_init+0x7c/0x80
Mar 28 22:16:29 jane kernel: [ 634.144303] [<ffffffff81f7a623>] x86_64_start_kernel+0x14a/0x16d
Mar 28 22:16:35 jane kernel: [ 640.382705] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [lxc-start:13935]
Mar 28 22:16:35 jane kernel: [ 640.391995] Hardware name: /DH67BL, BIOS BLH6710H.86A.0160.2012.1204.1156 12/04/2012
Mar 28 22:16:35 jane kernel: [ 640.394264] RSP: 0018:ffff880035fdb450 EFLAGS: 00000286
Mar 28 22:16:35 jane kernel: [ 640.397343] R10: ffff8806ebe6e000 R11: ffff88074a14a900 R12: ffffffff81f19038
Mar 28 22:16:35 jane kernel: [ 640.400416] CR2: 00000000006cd000 CR3: 00000000bd164000 CR4: 0000000000160670
Mar 28 22:16:35 jane kernel: [ 640.403462] 0000000081834477 0000000000000010 ffff8806ebe6fc28 ffff8806ebe6e198
Mar 28 22:16:35 jane kernel: [ 640.406467] [<ffffffff81750304>] ? netif_rx_internal+0x44/0x110
Mar 28 22:16:35 jane kernel: [ 640.409410] [<ffffffff81800cc7>] ip6_output+0x57/0x110
Mar 28 22:16:35 jane kernel: [ 640.412298] [<ffffffff81822800>] ? ipv6_icmp_sysctl_init+0x40/0x40
Mar 28 22:16:35 jane kernel: [ 640.414473] [<ffffffff81825f13>] __ipv6_dev_mc_dec+0xc3/0x120
Mar 28 22:16:35 jane kernel: [ 640.416697] [<ffffffff8175e812>] neigh_ifdown+0xc2/0xf0
Mar 28 22:16:35 jane kernel: [ 640.419674] [<ffffffff8174a7f5>] call_netdevice_notifiers_info+0x35/0x60
Mar 28 22:16:35 jane kernel: [ 640.422348] [<ffffffff8174c89b>] unregister_netdevice_many+0x1b/0xa0
Mar 28 22:16:35 jane kernel: [ 640.424774] [<ffffffff8108cf83>] ? ns_capable+0x13/0x20
Mar 28 22:16:35 jane kernel: [ 640.426952] [<ffffffff81761e00>] ? rtnetlink_rcv+0x30/0x30
Mar 28 22:16:35 jane kernel: [ 640.428956] [<ffffffff817861fd>] netlink_sendmsg+0x34d/0x3c0
Mar 28 22:16:35 jane kernel: [ 640.430924] [<ffffffff813a78c3>] ? aa_sk_perm+0x73/0x220
Mar 28 22:16:35 jane kernel: [ 640.432760] [<ffffffff81735082>] SyS_sendmsg+0x12/0x20
Mar 28 22:16:43 jane kernel: [ 648.375844] Modules linked in: drbg ansi_cprng authenc echainiv esp4 xfrm4_mode_transport l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppoe pppox cfg80211 xfrm_user xfrm_algo ipt_MASQUERADE nf_nat_masquerade_ipv4 binfmt_misc veth ip_set pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) softdog nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6table_filter ip6_tables iptable_filter xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables nfnetlink_log nfnetlink i915 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel gpio_ich ppdev kvm video drm_kms_helper irqbypass crct10dif_pclmul drm crc32_pclmul<4>[ 648.382563] Hardware name: /DH67BL, BIOS BLH6710H.86A.0160.2012.1204.1156 12/04/2012
Mar 28 22:16:43 jane kernel: [ 648.386087] RAX: 0000000000000101 RBX: ffffffff81f19034 RCX: 0000000000000101
Mar 28 22:16:43 jane kernel: [ 648.389698] FS: 0000000000000000(0000) GS:ffff88081f240000(0000) knlGS:0000000000000000
Mar 28 22:16:43 jane kernel: [ 648.393432] ffff8807f5a8bde8 ffffffff81873e89 ffff8807f5a8be20 ffffffff8175e947
Mar 28 22:16:43 jane kernel: [ 648.397333] [<ffffffff8175e947>] neigh_periodic_work+0x37/0x1d0
Mar 28 22:16:43 jane kernel: [ 648.401193] [<ffffffff810a3560>] ? kthread_park+0x60/0x60
Mar 28 22:17:03 jane kernel: [ 668.385704] Modules linked in: drbg ansi_cprng authenc echainiv esp4 xfrm4_mode_transport l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppoe pppox cfg80211 xfrm_user xfrm_algo ipt_MASQUERADE nf_nat_masquerade_ipv4 binfmt_misc veth ip_set pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) softdog nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6table_filter ip6_tables iptable_filter xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables nfnetlink_log nfnetlink i915 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel gpio_ich ppdev kvm video drm_kms_helper irqbypass crct10dif_pclmul drm crc32_pclmul<4>[ 668.397213] RIP: 0010:[<ffffffff810cf3af>] [<ffffffff810cf3af>] queued_write_lock_slowpath+0x3f/0x90
Mar 28 22:17:03 jane kernel: [ 668.401323] R10: ffff8806ebe6e000 R11: ffff88074a14a900 R12: ffffffff81f19038
Mar 28 22:17:03 jane kernel: [ 668.405351] Stack:
Mar 28 22:17:03 jane kernel: [ 668.409399] [<ffffffff81873e89>] _raw_write_lock_bh+0x29/0x30
Mar 28 22:17:03 jane kernel: [ 668.413354] [<ffffffff81800c06>] ip6_finish_output+0xa6/0x110
Mar 28 22:17:03 jane kernel: [ 668.417229] [<ffffffff81822800>] ? ipv6_icmp_sysctl_init+0x40/0x40
Mar 28 22:17:03 jane kernel: [ 668.421298] [<ffffffff81817b6b>] pndisc_destructor+0x5b/0x80
Mar 28 22:17:03 jane kernel: [ 668.425009] [<ffffffff8174a7f5>] call_netdevice_notifiers_info+0x35/0x60
Mar 28 22:17:03 jane kernel: [ 668.428342] [<ffffffff8176125e>] rtnl_delete_link+0x4e/0x80
Mar 28 22:17:03 jane kernel: [ 668.431261] [<ffffffff811f6168>] ? __kmalloc_node_track_caller+0x258/0x310
Mar 28 22:17:03 jane kernel: [ 668.433988] [<ffffffff81785e00>] netlink_unicast+0x190/0x240
Mar 28 22:17:03 jane kernel: [ 668.436506] [<ffffffff813a78c3>] ? aa_sk_perm+0x73/0x220
Mar 28 22:17:03 jane kernel: [ 668.438866] [<ffffffff818741c8>] entry_SYSCALL_64_fastpath+0x1c/0xbb
Mar 28 22:17:08 jane kernel: [ 672.854205] (t=15000 jiffies g=68579 c=68578 q=105197)
Mar 28 22:17:08 jane kernel: [ 672.856278] 0000000000000003 ffffffff81e5cec0 ffff88081f2c3dc0 ffffffff810b4269
Mar 28 22:17:08 jane kernel: [ 672.858575] [<ffffffff810b4269>] dump_cpu_task+0x39/0x40
Mar 28 22:17:08 jane kernel: [ 672.860853] [<ffffffff810b4cf9>] ? account_system_time+0x79/0x120
Mar 28 22:17:08 jane kernel: [ 672.864377] [<ffffffff8110211d>] tick_sched_timer+0x3d/0x70
Mar 28 22:17:08 jane kernel: [ 672.867934] [<ffffffff81877803>] smp_apic_timer_interrupt+0x43/0x60
Mar 28 22:17:08 jane kernel: [ 672.872859] [<ffffffff81750304>] ? netif_rx_internal+0x44/0x110
Mar 28 22:17:08 jane kernel: [ 672.878161] [<ffffffff81788ea3>] ? nf_iterate+0x63/0x80
Mar 28 22:17:08 jane kernel: [ 672.883475] [<ffffffff81824706>] igmp6_group_dropped+0x116/0x220
Mar 28 22:17:08 jane kernel: [ 672.888691] [<ffffffff818195e3>] ndisc_netdev_event+0xa3/0xf0
Mar 28 22:17:08 jane kernel: [ 672.894010] [<ffffffff8174c616>] rollback_registered_many+0x136/0x330
Mar 28 22:17:08 jane kernel: [ 672.898905] [<ffffffff8138c26f>] ? aa_capable+0xff/0x3b0
Mar 28 22:17:08 jane kernel: [ 672.903567] [<ffffffff81761e00>] ? rtnetlink_rcv+0x30/0x30
Mar 28 22:17:08 jane kernel: [ 672.908105] [<ffffffff813a81d1>] ? aa_sock_msg_perm+0x61/0x150
Mar 28 22:17:08 jane kernel: [ 672.912611] [<ffffffff81732754>] ? move_addr_to_user+0xb4/0xd0
Mar 28 22:17:08 jane kernel: [ 672.916170] INFO: rcu_bh self-detected stall on CPU
Mar 28 22:17:08 jane kernel: [ 672.916176] ffff8806f2556200 c807cdebe85a131f ffff88081f2c3da8 ffffffff810b1abf
Mar 28 22:17:08 jane kernel: [ 672.916182] [<ffffffff810b4269>] dump_cpu_task+0x39/0x40
Mar 28 22:17:08 jane kernel: [ 672.916188] [<ffffffff811020e0>] ? tick_sched_do_timer+0x30/0x30
Mar 28 22:17:08 jane kernel: [ 672.916194] [<ffffffff810f30c8>] hrtimer_interrupt+0xa8/0x1a0
Mar 28 22:17:08 jane kernel: [ 672.916201] [<ffffffff81873e89>] _raw_write_lock_bh+0x29/0x30
Mar 28 22:17:08 jane kernel: [ 672.916207] [<ffffffff81800c06>] ip6_finish_output+0xa6/0x110
Mar 28 22:17:08 jane kernel: [ 672.916213] [<ffffffff81822800>] ? ipv6_icmp_sysctl_init+0x40/0x40
Mar 28 22:17:08 jane kernel: [ 672.916220] [<ffffffff81817b6b>] pndisc_destructor+0x5b/0x80
Mar 28 22:17:08 jane kernel: [ 672.916225] [<ffffffff8174a7f5>] call_netdevice_notifiers_info+0x35/0x60
Mar 28 22:17:08 jane kernel: [ 672.916231] [<ffffffff8176125e>] rtnl_delete_link+0x4e/0x80
Mar 28 22:17:08 jane kernel: [ 672.916238] [<ffffffff811f6168>] ? __kmalloc_node_track_caller+0x258/0x310
Mar 28 22:17:08 jane kernel: [ 672.916244] [<ffffffff81785e00>] netlink_unicast+0x190/0x240
Mar 28 22:17:08 jane kernel: [ 672.916251] [<ffffffff813a78c3>] ? aa_sk_perm+0x73/0x220
Mar 28 22:17:08 jane kernel: [ 672.916258] [<ffffffff818741c8>] entry_SYSCALL_64_fastpath+0x1c/0xbb
Mar 28 22:17:08 jane kernel: [ 672.951377] (detected by 1, t=15002 jiffies, g=68579, c=68578, q=105198)
Mar 28 22:17:08 jane kernel: [ 672.953168] 0000000000000000 0000000000000000 0000000000000000 0000000000000003
Mar 28 22:17:08 jane kernel: [ 672.955086] [<ffffffff813a7beb>] ? aa_sock_perm+0x4b/0xe0
Mar 28 22:17:08 jane kernel: [ 672.956999] [<ffffffff818741c8>] ? entry_SYSCALL_64_fastpath+0x1c/0xbb
Mar 28 22:17:35 jane kernel: [ 700.379762] Modules linked in: drbg ansi_cprng authenc echainiv esp4 xfrm4_mode_transport l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppoe pppox cfg80211 xfrm_user xfrm_algo ipt_MASQUERADE nf_nat_masquerade_ipv4 binfmt_misc veth ip_set pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) softdog nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6table_filter ip6_tables iptable_filter xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables nfnetlink_log nfnetlink i915 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel gpio_ich ppdev kvm video drm_kms_helper irqbypass crct10dif_pclmul drm crc32_pclmul<0>[ 700.387264] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [lxc-start:13935]
Mar 28 22:17:35 jane kernel: [ 700.387315] task: ffff8806f2556200 ti: ffff880035fd8000 task.ti: ffff880035fd8000
Mar 28 22:17:35 jane kernel: [ 700.387321] RBP: ffff880035fdb460 R08: 000000000001ab60 R09: ffff8807fe803600
Mar 28 22:17:35 jane kernel: [ 700.387324] CR2: 00000000006cd000 CR3: 00000000bd164000 CR4: 0000000000160670
Mar 28 22:17:35 jane kernel: [ 700.387327] Call Trace:
Mar 28 22:17:35 jane kernel: [ 700.387339] [<ffffffff811b6448>] ? pcpu_alloc_area+0x2a8/0x3e0
Mar 28 22:17:35 jane kernel: [ 700.387347] [<ffffffff81824035>] NF_HOOK_THRESH.constprop.37+0x45/0xb0
Mar 28 22:17:35 jane kernel: [ 700.387354] [<ffffffff8182691f>] ipv6_dev_mc_dec+0x2f/0x60
Mar 28 22:17:35 jane kernel: [ 700.387360] [<ffffffff810a48c6>] raw_notifier_call_chain+0x16/0x20
Mar 28 22:17:35 jane kernel: [ 700.387367] [<ffffffff8174c89b>] unregister_netdevice_many+0x1b/0xa0
Mar 28 22:17:35 jane kernel: [ 700.387376] [<ffffffff81761ea4>] rtnetlink_rcv_msg+0xa4/0x230
Mar 28 22:17:35 jane kernel: [ 700.387384] [<ffffffff81761df8>] rtnetlink_rcv+0x28/0x30
Mar 28 22:17:35 jane kernel: [ 700.387391] [<ffffffff81734855>] ___sys_sendmsg+0x285/0x2a0
Mar 28 22:17:35 jane kernel: [ 700.387398] [<ffffffff81735082>] SyS_sendmsg+0x12/0x20
Mar 28 22:17:35 jane kernel: [ 700.442972] RSP: 0018:ffff8807f5a8bdb8 EFLAGS: 00000202
Mar 28 22:17:35 jane kernel: [ 700.445599] R13: ffffffff81f18f48 R14: ffffffff81f19034 R15: ffffffff81f18e40
Mar 28 22:17:35 jane kernel: [ 700.448277] ffff8807f5a8bdd8 ffffffff810cf3f0 ffff8807f60ece40 ffff8807fe99b000
Mar 28 22:17:35 jane kernel: [ 700.451044] [<ffffffff81873e89>] _raw_write_lock_bh+0x29/0x30
Mar 28 22:17:35 jane kernel: [ 700.453871] [<ffffffff810a365c>] kthread+0xfc/0x120
Click to expand...
 
Die IPv6 Geschichte mit Einsatz des Neighbor Discovery Proxy fahre ich erst seit einigen tagen. Ich werde das update in den nächsten tagen mal in Angriff nehmen und berichte dann ob das Problem weiterhin besteht.
 
  • Like
Reactions: fireon
Das Problem besteht weiterhin nach dem Upgrade auf 5.x. Nun mit kernel 4.13.16-1-pve und Proxmox 5.1-46. Die kernelmeldung wurde gerade eben allerdings nicht geworfen. Möglicherweise war der hardreboot diesmal schneller. Dennoch das gleiche verhalten. Container shutdown wird ausgeführt, Container ist nach 10 Sekunden immer noch nicht heruntergefahren und schwups zeigt sich der LXC Monitor mit 100% Auslastung. Dabei steigt der Load Average extrem rasant auf über 300 bis nach wenigen Sekunden der gesamte host nicht mehr reagiert.
 
Ich habe das ganze soeben mal genauer getestet und kam zu dem Ergebnis das es definitiv nicht mit dem tunnel in Verbindung steht sondern offenbar ein generelles Problem ist. Dazu habe ich einen host mit aktueller Proxmox Version (5.x) aufgesetzt und einen Container mit dem Debian 9.0 Standard Template angelegt. Dabei habe ich dem host die IPv6 Adresse fd07:d2b2:4d21:93f3:1ced:a2ab:f18b:1 zugewiesen.
Dem Container habe ich die fd07:d2b2:4d21:93f3:1ced:a2ab:f18b:2 zugewiesen.

Nun habe ich im Container mittels folgenden befehlen ein dummy interface angelegt und die IPv6 fd07:d2b2:4d21:93f3:1ced:a2ab:f18b:3 zugewiesen:
ip link add dummy0 type dummy
ip addr add fd07:d2b2:4d21:93f3:1ced:a2ab:f18b:3/120 dev dummy0
ip link set dummy0 up
ip neigh add proxy fd07:d2b2:4d21:93f3:1ced:a2ab:f18b:3 dev eth0


Wird der Container nun heruntergefahren tritt das Problem ein. Der Container fährt nicht herunter und der host verabschiedet sich.
Der kernel 4.13.16-1-pve meldet dabei folgendes:
Apr 2 17:41:36 debian kernel: [ 767.913129] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [lxc-start:1953]
Apr 2 17:41:36 debian kernel: [ 767.913518] Modules linked in: dummy veth tcp_diag inet_diag ip_set ip6table_filter ip6_tables iptable_filter softdog nfnetlink_log nfnetlink crct10dif_pclmul crc32_pclmul vboxvideo ghash_clmulni_intel snd_pcm pcbc ttm aesni_intel snd_timer aes_x86_64 drm_kms_helper joydev drm crypto_simd snd ppdev fb_sys_fops soundcore syscopyarea glue_helper sysfillrect sysimgblt cryptd input_leds mac_hid intel_rapl_perf parport_pc pcspkr vboxguest parport video serio_raw vhost_net vhost tap ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 hid_generic usbhid hid ahci libahci psmouse i2c_piix4 e1000
Apr 2 17:41:36 debian kernel: [ 767.913547] CPU: 3 PID: 1953 Comm: lxc-start Not tainted 4.13.16-1-pve #1
Apr 2 17:41:36 debian kernel: [ 767.913548] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Apr 2 17:41:36 debian kernel: [ 767.913549] task: ffff9663078d1740 task.stack: ffffa6f944e08000
Apr 2 17:41:36 debian kernel: [ 767.913552] RIP: 0010:queued_write_lock_slowpath+0x52/0x90
Apr 2 17:41:36 debian kernel: [ 767.913553] RSP: 0018:ffffa6f944e0b3a0 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff10
Apr 2 17:41:36 debian kernel: [ 767.913554] RAX: 00000000000001ff RBX: ffffffff8da06814 RCX: 00000000000000ff
Apr 2 17:41:36 debian kernel: [ 767.913554] RDX: 00000000000001ff RSI: 0000000000000100 RDI: ffffffff8da06814
Apr 2 17:41:36 debian kernel: [ 767.913555] RBP: ffffa6f944e0b3b0 R08: ffff96635f3a5de0 R09: ffff9662ff92da00
Apr 2 17:41:36 debian kernel: [ 767.913556] R10: ffff9662ff92da00 R11: ffff9663050d7300 R12: ffffffff8da06818
Apr 2 17:41:36 debian kernel: [ 767.913556] R13: 0000000000000001 R14: ffff96630f0f8000 R15: ffff9662fc4e1c00
Apr 2 17:41:36 debian kernel: [ 767.913557] FS: 00007fb3af51a780(0000) GS:ffff96635f380000(0000) knlGS:0000000000000000
Apr 2 17:41:36 debian kernel: [ 767.913558] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 2 17:41:36 debian kernel: [ 767.913559] CR2: 000055b565b92000 CR3: 00000000c78f8000 CR4: 00000000000406e0
Apr 2 17:41:36 debian kernel: [ 767.913562] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 2 17:41:36 debian kernel: [ 767.913562] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 2 17:41:36 debian kernel: [ 767.913563] Call Trace:
Apr 2 17:41:36 debian kernel: [ 767.913566] _raw_write_lock_bh+0x29/0x30
Apr 2 17:41:36 debian kernel: [ 767.913568] __neigh_create+0x1fc/0x5d0
Apr 2 17:41:36 debian kernel: [ 767.913569] ? mroute6_socket+0x6a/0x90
Apr 2 17:41:36 debian kernel: [ 767.913571] ip6_finish_output2+0x214/0x4f0
Apr 2 17:41:36 debian kernel: [ 767.913573] ip6_finish_output+0xb1/0x1c0
Apr 2 17:41:36 debian kernel: [ 767.913574] ? ip6_finish_output+0xb1/0x1c0
Apr 2 17:41:36 debian kernel: [ 767.913575] ? dst_alloc+0x4c/0xa0
Apr 2 17:41:36 debian kernel: [ 767.913576] ip6_output+0x70/0x110
Apr 2 17:41:36 debian kernel: [ 767.913578] NF_HOOK.constprop.38+0x45/0xb0
Apr 2 17:41:36 debian kernel: [ 767.913579] ? icmp6_dst_alloc+0xe0/0x140
Apr 2 17:41:36 debian kernel: [ 767.913580] igmp6_send+0x26c/0x350
Apr 2 17:41:36 debian kernel: [ 767.913581] ? __hw_addr_del_entry+0x88/0xa0
Apr 2 17:41:36 debian kernel: [ 767.913583] igmp6_group_dropped+0x10b/0x1f0
Apr 2 17:41:36 debian kernel: [ 767.913584] ? igmp6_group_dropped+0x10b/0x1f0
Apr 2 17:41:36 debian kernel: [ 767.913585] __ipv6_dev_mc_dec+0xc1/0x120
Apr 2 17:41:36 debian kernel: [ 767.913587] ipv6_dev_mc_dec+0x2f/0x60
Apr 2 17:41:36 debian kernel: [ 767.913588] pndisc_destructor+0x64/0x90
Apr 2 17:41:36 debian kernel: [ 767.913589] neigh_ifdown+0xc2/0xf0
Apr 2 17:41:36 debian kernel: [ 767.913590] ? ndisc_error_report+0x40/0x40
Apr 2 17:41:36 debian kernel: [ 767.913591] ? neigh_ifdown+0xc2/0xf0
Apr 2 17:41:36 debian kernel: [ 767.913592] ndisc_netdev_event+0xda/0xf0
Apr 2 17:41:36 debian kernel: [ 767.913593] notifier_call_chain+0x4c/0x70
Apr 2 17:41:36 debian kernel: [ 767.913595] raw_notifier_call_chain+0x16/0x20
Apr 2 17:41:36 debian kernel: [ 767.913596] call_netdevice_notifiers_info+0x35/0x60
Apr 2 17:41:36 debian kernel: [ 767.913597] dev_close_many+0xc7/0x130
Apr 2 17:41:36 debian kernel: [ 767.913598] rollback_registered_many+0x132/0x3f0
Apr 2 17:41:36 debian kernel: [ 767.913599] unregister_netdevice_many+0x1e/0xb0
Apr 2 17:41:36 debian kernel: [ 767.913600] rtnl_delete_link+0x4e/0x80
Apr 2 17:41:36 debian kernel: [ 767.913602] rtnl_dellink+0xd3/0x1e0
Apr 2 17:41:36 debian kernel: [ 767.913604] ? ns_capable+0x13/0x20
Apr 2 17:41:36 debian kernel: [ 767.913605] rtnetlink_rcv_msg+0xf4/0x220
Apr 2 17:41:36 debian kernel: [ 767.913606] ? aa_label_sk_perm+0x12a/0x150
Apr 2 17:41:36 debian kernel: [ 767.913608] ? rtnl_newlink+0x940/0x940
Apr 2 17:41:36 debian kernel: [ 767.913610] netlink_rcv_skb+0xec/0x120
Apr 2 17:41:36 debian kernel: [ 767.913611] rtnetlink_rcv+0x28/0x30
Apr 2 17:41:36 debian kernel: [ 767.913612] netlink_unicast+0x192/0x230
Apr 2 17:41:36 debian kernel: [ 767.913627] netlink_sendmsg+0x2d2/0x3c0
Apr 2 17:41:36 debian kernel: [ 767.913629] sock_sendmsg+0x3e/0x50
Apr 2 17:41:36 debian kernel: [ 767.913630] ___sys_sendmsg+0x2e9/0x300
Apr 2 17:41:36 debian kernel: [ 767.913631] ? aa_sk_perm+0x53/0x150
Apr 2 17:41:36 debian kernel: [ 767.913633] ? __check_object_size+0xb3/0x190
Apr 2 17:41:36 debian kernel: [ 767.913634] ? _copy_to_user+0x2a/0x40
Apr 2 17:41:36 debian kernel: [ 767.913635] ? move_addr_to_user+0xc0/0xe0
Apr 2 17:41:36 debian kernel: [ 767.913636] ? entry_SYSCALL_64_after_hwframe+0x11a/0x139
Apr 2 17:41:36 debian kernel: [ 767.913637] ? entry_SYSCALL_64_after_hwframe+0x113/0x139
Apr 2 17:41:36 debian kernel: [ 767.913639] __sys_sendmsg+0x54/0x90
Apr 2 17:41:36 debian kernel: [ 767.913640] ? __sys_sendmsg+0x54/0x90
Apr 2 17:41:36 debian kernel: [ 767.913641] SyS_sendmsg+0x12/0x20
Apr 2 17:41:36 debian kernel: [ 767.913642] entry_SYSCALL_64_fastpath+0x24/0xab
Apr 2 17:41:36 debian kernel: [ 767.913643] RIP: 0033:0x7fb3aea01e47
Apr 2 17:41:36 debian kernel: [ 767.913644] RSP: 002b:00007fff03c23bd8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
Apr 2 17:41:36 debian kernel: [ 767.913645] RAX: ffffffffffffffda RBX: 000000000000000e RCX: 00007fb3aea01e47
Apr 2 17:41:36 debian kernel: [ 767.913646] RDX: 0000000000000000 RSI: 00007fff03c23c00 RDI: 000000000000000e
Apr 2 17:41:36 debian kernel: [ 767.913646] RBP: 00007fb3af0ef5d0 R08: 00007fff03c23c70 R09: 0000000000000020
Apr 2 17:41:36 debian kernel: [ 767.913647] R10: 00000000000000a0 R11: 0000000000000246 R12: 000055b565b95c58
Apr 2 17:41:36 debian kernel: [ 767.913648] R13: 00007fb3af0ef2a5 R14: 000055b565b95c10 R15: 000055b565b734a0
Apr 2 17:41:36 debian kernel: [ 767.913648] Code: 75 0d ba ff 00 00 00 f0 0f b1 13 85 c0 74 33 f0 81 03 00 01 00 00 b9 ff 00 00 00 be 00 01 00 00 8b 03 3d 00 01 00 00 74 0c f3 90 <8b> 13 81 fa 00 01 00 00 75 f4 89 f0 f0 0f b1 0b 3d 00 01 00 00
Click to expand...
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom