So I had posted another thread about after a kernel panic, docker host access to custom networks doesn't work until docker is stopped/restarted on 6.9.0
After further investigation and setting up syslogging, it apperas that it may actually be that host access that's CAUSING the kernel panic?
EDIT: 3/16 - I guess I needed to create a VLAN for my dockers with static IPs, so far that's working, so it's probably not HOST access causing the issue, but rather br0 static IPs being set. See following posts below.
Here's my last kernel panic that thankfully got logged to syslog. It references macvlan and netfilter. I don't know enough to be super useful here, but this is my docker setup.
Mar 12 03:57:07 Server kernel: ------------[ cut here ]------------ Mar 12 03:57:07 Server kernel: WARNING: CPU: 17 PID: 626 at net/netfilter/nf_nat_core.c:614 nf_nat_setup_info+0x6c/0x652 [nf_nat] Mar 12 03:57:07 Server kernel: Modules linked in: ccp macvlan xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_MASQUERADE iptable_nat nf_nat xfs md_mod ip6table_filter ip6_tables iptable_filter ip_tables bonding igb i2c_algo_bit cp210x usbserial sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd ipmi_ssif isci glue_helper mpt3sas i2c_i801 rapl libsas i2c_smbus input_leds i2c_core ahci intel_cstate raid_class led_class acpi_ipmi intel_uncore libahci scsi_transport_sas wmi ipmi_si button [last unloaded: ipmi_devintf] Mar 12 03:57:07 Server kernel: CPU: 17 PID: 626 Comm: kworker/17:2 Tainted: G W 5.10.19-Unraid #1 Mar 12 03:57:07 Server kernel: Hardware name: Supermicro PIO-617R-TLN4F+-ST031/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.2 03/04/2015 Mar 12 03:57:07 Server kernel: Workqueue: events macvlan_process_broadcast [macvlan] Mar 12 03:57:07 Server kernel: RIP: 0010:nf_nat_setup_info+0x6c/0x652 [nf_nat] Mar 12 03:57:07 Server kernel: Code: 89 fb 49 89 f6 41 89 d4 76 02 0f 0b 48 8b 93 80 00 00 00 89 d0 25 00 01 00 00 45 85 e4 75 07 89 d0 25 80 00 00 00 85 c0 74 07 <0f> 0b e9 1f 05 00 00 48 8b 83 90 00 00 00 4c 8d 6c 24 20 48 8d 73 Mar 12 03:57:07 Server kernel: RSP: 0018:ffffc90006778c38 EFLAGS: 00010202 Mar 12 03:57:07 Server kernel: RAX: 0000000000000080 RBX: ffff88837c8303c0 RCX: ffff88811e834880 Mar 12 03:57:07 Server kernel: RDX: 0000000000000180 RSI: ffffc90006778d14 RDI: ffff88837c8303c0 Mar 12 03:57:07 Server kernel: RBP: ffffc90006778d00 R08: 0000000000000000 R09: ffff889083c68160 Mar 12 03:57:07 Server kernel: R10: 0000000000000158 R11: ffff8881e79c1400 R12: 0000000000000000 Mar 12 03:57:07 Server kernel: R13: 0000000000000000 R14: ffffc90006778d14 R15: 0000000000000001 Mar 12 03:57:07 Server kernel: FS: 0000000000000000(0000) GS:ffff88903fc40000(0000) knlGS:0000000000000000 Mar 12 03:57:07 Server kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 12 03:57:07 Server kernel: CR2: 000000c000b040b8 CR3: 000000000200c005 CR4: 00000000001706e0 Mar 12 03:57:07 Server kernel: Call Trace: Mar 12 03:57:07 Server kernel: <IRQ> Mar 12 03:57:07 Server kernel: ? activate_task+0x9/0x12 Mar 12 03:57:07 Server kernel: ? resched_curr+0x3f/0x4c Mar 12 03:57:07 Server kernel: ? ipt_do_table+0x49b/0x5c0 [ip_tables] Mar 12 03:57:07 Server kernel: ? try_to_wake_up+0x1b0/0x1e5 Mar 12 03:57:07 Server kernel: nf_nat_alloc_null_binding+0x71/0x88 [nf_nat] Mar 12 03:57:07 Server kernel: nf_nat_inet_fn+0x91/0x182 [nf_nat] Mar 12 03:57:07 Server kernel: nf_hook_slow+0x39/0x8e Mar 12 03:57:07 Server kernel: nf_hook.constprop.0+0xb1/0xd8 Mar 12 03:57:07 Server kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe Mar 12 03:57:07 Server kernel: ip_local_deliver+0x49/0x75 Mar 12 03:57:07 Server kernel: ip_sabotage_in+0x43/0x4d Mar 12 03:57:07 Server kernel: nf_hook_slow+0x39/0x8e Mar 12 03:57:07 Server kernel: nf_hook.constprop.0+0xb1/0xd8 Mar 12 03:57:07 Server kernel: ? l3mdev_l3_rcv.constprop.0+0x50/0x50 Mar 12 03:57:07 Server kernel: ip_rcv+0x41/0x61 Mar 12 03:57:07 Server kernel: __netif_receive_skb_one_core+0x74/0x95 Mar 12 03:57:07 Server kernel: process_backlog+0xa3/0x13b Mar 12 03:57:07 Server kernel: net_rx_action+0xf4/0x29d Mar 12 03:57:07 Server kernel: __do_softirq+0xc4/0x1c2 Mar 12 03:57:07 Server kernel: asm_call_irq_on_stack+0x12/0x20 Mar 12 03:57:07 Server kernel: </IRQ> Mar 12 03:57:07 Server kernel: do_softirq_own_stack+0x2c/0x39 Mar 12 03:57:07 Server kernel: do_softirq+0x3a/0x44 Mar 12 03:57:07 Server kernel: netif_rx_ni+0x1c/0x22 Mar 12 03:57:07 Server kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Mar 12 03:57:07 Server kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Mar 12 03:57:07 Server kernel: process_one_work+0x13c/0x1d5 Mar 12 03:57:07 Server kernel: worker_thread+0x18b/0x22f Mar 12 03:57:07 Server kernel: ? process_scheduled_works+0x27/0x27 Mar 12 03:57:07 Server kernel: kthread+0xe5/0xea Mar 12 03:57:07 Server kernel: ? __kthread_bind_mask+0x57/0x57 Mar 12 03:57:07 Server kernel: ret_from_fork+0x22/0x30 Mar 12 03:57:07 Server kernel: ---[ end trace b3ca21ac5f2c2720 ]---
Recommended Comments
Posted by bonienl,
13 reactions
Go to this comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.