This morning I found the following lines in the log:

 

Quote

Apr 23 02:30:20 LSL-NAS kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
Apr 23 02:30:20 LSL-NAS kernel: IP: tcp_push+0x4e/0xee
Apr 23 02:30:20 LSL-NAS kernel: PGD 0 P4D 0 
Apr 23 02:30:20 LSL-NAS kernel: Oops: 0002 [#1] PREEMPT SMP PTI
Apr 23 02:30:20 LSL-NAS kernel: Modules linked in: macvlan xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod nct6775 hwmon_vid bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_i801 i2c_core intel_cstate alx intel_uncore ahci libahci intel_rapl_perf video mdio backlight button acpi_cpufreq
Apr 23 02:30:20 LSL-NAS kernel: CPU: 3 PID: 12092 Comm: deluged Not tainted 4.14.26-unRAID #1
Apr 23 02:30:20 LSL-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H87M, BIOS P2.60 01/08/2016
Apr 23 02:30:20 LSL-NAS kernel: task: ffff8801af568e00 task.stack: ffffc9000140c000
Apr 23 02:30:20 LSL-NAS kernel: RIP: 0010:tcp_push+0x4e/0xee
Apr 23 02:30:20 LSL-NAS kernel: RSP: 0018:ffffc9000140fc70 EFLAGS: 00010246
Apr 23 02:30:20 LSL-NAS kernel: RAX: 0000000000000000 RBX: 00000000000005a0 RCX: 0000000000000000
Apr 23 02:30:20 LSL-NAS kernel: RDX: 0000000000000000 RSI: 0000000000004040 RDI: ffff8800b47e0000
Apr 23 02:30:20 LSL-NAS kernel: RBP: 0000000000000000 R08: 00000000000005a0 R09: ffffffff8151db00
Apr 23 02:30:20 LSL-NAS kernel: R10: ffff8800b47e0158 R11: 0000000000000000 R12: ffff8800b47e0000
Apr 23 02:30:20 LSL-NAS kernel: R13: 0000000000000000 R14: ffff88006a620200 R15: 00000000ffffffe0
Apr 23 02:30:20 LSL-NAS kernel: FS:  000014f523d5bae8(0000) GS:ffff88021e380000(0000) knlGS:0000000000000000
Apr 23 02:30:20 LSL-NAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 23 02:30:20 LSL-NAS kernel: CR2: 0000000000000038 CR3: 00000001bbd00003 CR4: 00000000001606e0
Apr 23 02:30:20 LSL-NAS kernel: Call Trace:
Apr 23 02:30:20 LSL-NAS kernel: tcp_sendmsg_locked+0xa53/0xbac
Apr 23 02:30:20 LSL-NAS kernel: tcp_sendmsg+0x23/0x35
Apr 23 02:30:20 LSL-NAS kernel: sock_sendmsg+0x14/0x1e
Apr 23 02:30:20 LSL-NAS kernel: ___sys_sendmsg+0x1ab/0x229
Apr 23 02:30:20 LSL-NAS kernel: ? sock_poll+0x6d/0x76
Apr 23 02:30:20 LSL-NAS kernel: ? ep_send_events_proc+0xaa/0x163
Apr 23 02:30:20 LSL-NAS kernel: ? seccomp_run_filters+0xdc/0x106
Apr 23 02:30:20 LSL-NAS kernel: ? ep_scan_ready_list.constprop.2+0x17a/0x19a
Apr 23 02:30:20 LSL-NAS kernel: ? __seccomp_filter+0x26/0x1c5
Apr 23 02:30:20 LSL-NAS kernel: ? __sys_sendmsg+0x3c/0x5d
Apr 23 02:30:20 LSL-NAS kernel: __sys_sendmsg+0x3c/0x5d
Apr 23 02:30:20 LSL-NAS kernel: do_syscall_64+0xfe/0x107
Apr 23 02:30:20 LSL-NAS kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Apr 23 02:30:20 LSL-NAS kernel: RIP: 0033:0x14f523d02f33
Apr 23 02:30:20 LSL-NAS kernel: RSP: 002b:000014f523d5ac28 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
Apr 23 02:30:20 LSL-NAS kernel: RAX: ffffffffffffffda RBX: 000014f523d5bae8 RCX: 000014f523d02f33
Apr 23 02:30:20 LSL-NAS kernel: RDX: 0000000000004000 RSI: 000014f523d5ac78 RDI: 0000000000000043
Apr 23 02:30:20 LSL-NAS kernel: RBP: 000000000000002e R08: 0000000000000000 R09: 0000000000000000
Apr 23 02:30:20 LSL-NAS kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000004000
Apr 23 02:30:20 LSL-NAS kernel: R13: 000000000000003c R14: 000014f523d5b1f8 R15: 0000000000000000
Apr 23 02:30:20 LSL-NAS kernel: Code: d0 75 02 31 c0 41 89 f3 41 81 e3 00 80 00 00 74 1a 44 8b 8f 68 05 00 00 41 d1 e9 44 2b 8f 6c 06 00 00 44 03 8f 74 06 00 00 79 10 <80> 48 38 08 8b 8f 6c 06 00 00 89 8f 74 06 00 00 40 80 e6 01 74 
Apr 23 02:30:20 LSL-NAS kernel: RIP: tcp_push+0x4e/0xee RSP: ffffc9000140fc70
Apr 23 02:30:20 LSL-NAS kernel: CR2: 0000000000000038

 

Deluge wasn't responding this morning (webui), so I restarted the docker, and it was fine. I'm not sure both are related, but deluge is mentioned in the above log.

 

Any idea? I haven't seen this before, and I never had problem with the deluge docker not responding.

I updated to 6.5.0 late last week. I was on 6.4.x before that.

 

thank you!

Edited April 23, 20188 yr by LSL1337

It's a known kernel bug on v6.5, update to latest rc.

thank you, i will wait until the next stable.

Update to the latest "stable", 6.5.1 which came out today: