So basically as the title says my sever is going unresponsive every few days. When it freezes I can no longer get anything on the screen or connect to it over the network when this happens. A simple restart solves the problem for a few days. Its been doing this on and off for a few months now. I am running version 6.11.5 right now but it has been doing this on a few versions now. I finally caught a log of it crashing and I will put a snippet below. There is more of the log if that would be helpful to you.

 

I'm not really sure where to even start with this. Any help would be appreciated.

 

Jan  5 11:39:51 DELL-R510 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
Jan  5 11:39:51 DELL-R510 kernel: #PF: supervisor write access in kernel mode
Jan  5 11:39:51 DELL-R510 kernel: #PF: error_code(0x0002) - not-present page
Jan  5 11:39:51 DELL-R510 kernel: PGD 0 P4D 0 
Jan  5 11:39:51 DELL-R510 kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Jan  5 11:39:51 DELL-R510 kernel: CPU: 17 PID: 27506 Comm: kworker/17:3 Tainted: P        W IO      5.19.17-Unraid #2
Jan  5 11:39:51 DELL-R510 kernel: Hardware name: Dell Inc. PowerEdge R510/0DPRKF, BIOS 1.14.0 05/30/2018
Jan  5 11:39:51 DELL-R510 kernel: Workqueue: events drain_vmap_area_work
Jan  5 11:39:51 DELL-R510 kernel: RIP: 0010:__purge_vmap_area_lazy+0x45d/0x4fd
Jan  5 11:39:51 DELL-R510 kernel: Code: 88 82 48 8d 7d 10 48 89 45 18 48 89 45 20 48 89 39 4c 89 4c 24 08 e8 61 38 28 00 31 d2 4c 8b 4c 24 08 48 89 55 38 49 8b 45 00 <4c> 89 48 08 4c 89 6d 30 48 89 45 28 4d 89 4d 00 49 89 ed 4d 85 ed
Jan  5 11:39:51 DELL-R510 kernel: RSP: 0018:ffffc9000641fe10 EFLAGS: 00010246
Jan  5 11:39:51 DELL-R510 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88817ed90720
Jan  5 11:39:51 DELL-R510 kernel: RDX: 0000000000000000 RSI: ffffffff8288f660 RDI: ffff888195e41150
Jan  5 11:39:51 DELL-R510 kernel: RBP: ffff888195e41140 R08: ffff88817ed90718 R09: ffff888195e41168
Jan  5 11:39:51 DELL-R510 kernel: R10: ffff888188604340 R11: fefefefefefefeff R12: ffff888104a561a8
Jan  5 11:39:51 DELL-R510 kernel: R13: ffff88817ed90730 R14: ffffc90008440000 R15: ffffc9000641fe48
Jan  5 11:39:51 DELL-R510 kernel: FS:  0000000000000000(0000) GS:ffff888343c00000(0000) knlGS:0000000000000000
Jan  5 11:39:51 DELL-R510 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan  5 11:39:51 DELL-R510 kernel: CR2: 0000000000000008 CR3: 000000000220a004 CR4: 00000000000206e0
Jan  5 11:39:51 DELL-R510 kernel: Call Trace:
Jan  5 11:39:51 DELL-R510 kernel: <TASK>
Jan  5 11:39:51 DELL-R510 kernel: drain_vmap_area_work+0x20/0x4f
Jan  5 11:39:51 DELL-R510 kernel: process_one_work+0x1a8/0x295
Jan  5 11:39:51 DELL-R510 kernel: worker_thread+0x18b/0x244
Jan  5 11:39:51 DELL-R510 kernel: ? rescuer_thread+0x281/0x281
Jan  5 11:39:51 DELL-R510 kernel: kthread+0xe4/0xef
Jan  5 11:39:51 DELL-R510 kernel: ? kthread_complete_and_exit+0x1b/0x1b
Jan  5 11:39:51 DELL-R510 kernel: ret_from_fork+0x1f/0x30
Jan  5 11:39:51 DELL-R510 kernel: </TASK>
Jan  5 11:39:51 DELL-R510 kernel: Modules linked in: vhost_net vhost tap kvm_intel kvm macvlan md_mod xt_mark nvidia_uvm(PO) xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle tun vhost_iotlb veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls bnx2 nvidia_drm(PO) nvidia_modeset(PO) ipmi_ssif intel_powerclamp coretemp nvidia(PO) mgag200 drm_shmem_helper i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd drm cryptd intel_cstate backlight intel_uncore mpt3sas input_leds ata_piix joydev led_class i2c_core raid_class syscopyarea sysfillrect scsi_transport_sas sysimgblt fb_sys_fops wmi ipmi_si acpi_power_meter button unix [last unloaded: md_mod]
Jan  5 11:39:51 DELL-R510 kernel: CR2: 0000000000000008
Jan  5 11:39:51 DELL-R510 kernel: ---[ end trace 0000000000000000 ]---

 

Edited January 6, 20233 yr by Nick D

6 hours ago, Nick D said:

There is more of the log if that would be helpful to you.

It could, or enable the syslog server and post that after a crash.

Hey,

Here is my syslog. I have Mirror syslog to flash turned on and this is the log from it. I believe the system crashed at Jan 5 11:39:51 just by guessing at my logs. I also know my plex server was no longer reachable at 13:50 according to my Home assistant plex integration. There are probably a few other freeze up's in that log as well but I cant speak to the times. 

 

thanks again

syslog (1)

Jan  4 16:02:37 DELL-R510 kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Jan  4 16:02:37 DELL-R510 kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 or later and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right))

Alright I switched my docker to IPVLAN. I will report back on the results over the next few days.

 

Thanks for the Help