Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Intermittent IRQ errors in logs

Featured Replies

Hi there,

 

Recently I've been seeing errors similar to:

Aug  4 09:18:14 iamserver kernel: rcu: INFO: rcu_sched self-detected stall on CPU
Aug  4 09:18:14 iamserver kernel: rcu: 	0-....: (779698 ticks this GP) idle=08a/1/0x4000000000000002 softirq=90781609/90781610 fqs=184365 
Aug  4 09:18:14 iamserver kernel: rcu: 	 (t=780014 jiffies g=223095361 q=211077)
Aug  4 09:18:14 iamserver kernel: NMI backtrace for cpu 0
Aug  4 09:18:14 iamserver kernel: CPU: 0 PID: 31451 Comm: containerd Tainted: P      D W  O      4.19.107-Unraid #1
Aug  4 09:18:14 iamserver kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Taichi Ultimate, BIOS P3.90 01/10/2020
Aug  4 09:18:14 iamserver kernel: Call Trace:
Aug  4 09:18:14 iamserver kernel: <IRQ>
Aug  4 09:18:14 iamserver kernel: dump_stack+0x67/0x83
Aug  4 09:18:14 iamserver kernel: nmi_cpu_backtrace+0x71/0x83
Aug  4 09:18:14 iamserver kernel: ? lapic_can_unplug_cpu+0x97/0x97
Aug  4 09:18:14 iamserver kernel: nmi_trigger_cpumask_backtrace+0x57/0xd4
Aug  4 09:18:14 iamserver kernel: rcu_dump_cpu_stacks+0x8b/0xb4
Aug  4 09:18:14 iamserver kernel: rcu_check_callbacks+0x296/0x5a0
Aug  4 09:18:14 iamserver kernel: update_process_times+0x24/0x47
Aug  4 09:18:14 iamserver kernel: tick_sched_timer+0x36/0x64
Aug  4 09:18:14 iamserver kernel: __hrtimer_run_queues+0xb7/0x10b
Aug  4 09:18:14 iamserver kernel: ? tick_sched_handle.isra.0+0x2f/0x2f
Aug  4 09:18:14 iamserver kernel: hrtimer_interrupt+0xf4/0x20e
Aug  4 09:18:14 iamserver kernel: smp_apic_timer_interrupt+0x7b/0x93
Aug  4 09:18:14 iamserver kernel: apic_timer_interrupt+0xf/0x20
Aug  4 09:18:14 iamserver kernel: </IRQ>
Aug  4 09:18:14 iamserver kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x67/0x171
Aug  4 09:18:14 iamserver kernel: Code: 01 00 00 0f 42 f0 8b 07 30 e4 09 c6 f7 c6 00 ff ff ff 74 0e 81 e6 00 ff 00 00 75 1a c6 47 01 00 eb 14 85 f6 74 0a 8b 07 84 c0 <74> 04 f3 90 eb f6 66 c7 07 01 00 c3 48 c7 c2 40 07 02 00 65 48 03
Aug  4 09:18:14 iamserver kernel: RSP: 0018:ffffc9000a48bd78 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
Aug  4 09:18:14 iamserver kernel: RAX: 0000000000000101 RBX: ffffc900035bc948 RCX: 000000009b3fabc7
Aug  4 09:18:14 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffc900035bc944
Aug  4 09:18:14 iamserver kernel: RBP: ffffc900035bc944 R08: 000000000270ac88 R09: 0000000000000000
Aug  4 09:18:14 iamserver kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Aug  4 09:18:14 iamserver kernel: R13: 00000000ffffffff R14: 0000000000000001 R15: 0000000000000001
Aug  4 09:18:14 iamserver kernel: _raw_spin_lock+0x16/0x19
Aug  4 09:18:14 iamserver kernel: futex_wake+0x91/0x147
Aug  4 09:18:14 iamserver kernel: do_futex+0x20e/0x9dc
Aug  4 09:18:14 iamserver kernel: ? wake_up_q+0x2d/0x48
Aug  4 09:18:14 iamserver kernel: ? rwsem_wake+0x9b/0xbe
Aug  4 09:18:14 iamserver kernel: __se_sys_futex+0x131/0x156
Aug  4 09:18:14 iamserver kernel: ? __do_page_fault+0x36d/0x3ff
Aug  4 09:18:14 iamserver kernel: do_syscall_64+0x57/0xf2
Aug  4 09:18:14 iamserver kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug  4 09:18:14 iamserver kernel: RIP: 0033:0x45f623
Aug  4 09:18:14 iamserver kernel: Code: 24 20 c3 cc cc cc cc 48 8b 7c 24 08 8b 74 24 10 8b 54 24 14 4c 8b 54 24 18 4c 8b 44 24 20 44 8b 4c 24 28 b8 ca 00 00 00 0f 05 <89> 44 24 30 c3 cc cc cc cc cc cc cc cc 8b 7c 24 08 48 8b 74 24 10
Aug  4 09:18:14 iamserver kernel: RSP: 002b:000014e0d5f7ab98 EFLAGS: 00000206 ORIG_RAX: 00000000000000ca
Aug  4 09:18:14 iamserver kernel: RAX: ffffffffffffffda RBX: 000000c0004b9000 RCX: 000000000045f623
Aug  4 09:18:14 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000081 RDI: 000000000270ac88
Aug  4 09:18:14 iamserver kernel: RBP: 000014e0d5f7abe8 R08: 0000000000000000 R09: 0000000000000000
Aug  4 09:18:14 iamserver kernel: R10: 0000000000000000 R11: 0000000000000206 R12: ffffffffffffffff
Aug  4 09:18:14 iamserver kernel: R13: 0000000000000002 R14: 0000000000000001 R15: 0000000000000200
Aug  4 09:18:19 iamserver kernel: rcu: INFO: rcu_bh self-detected stall on CPU
Aug  4 09:18:19 iamserver kernel: rcu: 	0-....: (795572 ticks this GP) idle=08a/1/0x4000000000000002 softirq=90776120/90781610 fqs=186292 
Aug  4 09:18:19 iamserver kernel: rcu: 	 (t=780014 jiffies g=21013 q=2)
Aug  4 09:18:19 iamserver kernel: NMI backtrace for cpu 0
Aug  4 09:18:19 iamserver kernel: CPU: 0 PID: 31451 Comm: containerd Tainted: P      D W  O      4.19.107-Unraid #1
Aug  4 09:18:19 iamserver kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Taichi Ultimate, BIOS P3.90 01/10/2020
Aug  4 09:18:19 iamserver kernel: Call Trace:
Aug  4 09:18:19 iamserver kernel: <IRQ>
Aug  4 09:18:19 iamserver kernel: dump_stack+0x67/0x83
Aug  4 09:18:19 iamserver kernel: nmi_cpu_backtrace+0x71/0x83
Aug  4 09:18:19 iamserver kernel: ? lapic_can_unplug_cpu+0x97/0x97
Aug  4 09:18:19 iamserver kernel: nmi_trigger_cpumask_backtrace+0x57/0xd4
Aug  4 09:18:19 iamserver kernel: rcu_dump_cpu_stacks+0x8b/0xb4
Aug  4 09:18:19 iamserver kernel: rcu_check_callbacks+0x296/0x5a0
Aug  4 09:18:19 iamserver kernel: update_process_times+0x24/0x47
Aug  4 09:18:19 iamserver kernel: tick_sched_timer+0x36/0x64
Aug  4 09:18:19 iamserver kernel: __hrtimer_run_queues+0xb7/0x10b
Aug  4 09:18:19 iamserver kernel: ? tick_sched_handle.isra.0+0x2f/0x2f
Aug  4 09:18:19 iamserver kernel: hrtimer_interrupt+0xf4/0x20e
Aug  4 09:18:19 iamserver kernel: smp_apic_timer_interrupt+0x7b/0x93
Aug  4 09:18:19 iamserver kernel: apic_timer_interrupt+0xf/0x20
Aug  4 09:18:19 iamserver kernel: </IRQ>
Aug  4 09:18:19 iamserver kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x67/0x171
Aug  4 09:18:19 iamserver kernel: Code: 01 00 00 0f 42 f0 8b 07 30 e4 09 c6 f7 c6 00 ff ff ff 74 0e 81 e6 00 ff 00 00 75 1a c6 47 01 00 eb 14 85 f6 74 0a 8b 07 84 c0 <74> 04 f3 90 eb f6 66 c7 07 01 00 c3 48 c7 c2 40 07 02 00 65 48 03
Aug  4 09:18:19 iamserver kernel: RSP: 0018:ffffc9000a48bd78 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
Aug  4 09:18:19 iamserver kernel: RAX: 0000000000000101 RBX: ffffc900035bc948 RCX: 000000009b3fabc7
Aug  4 09:18:19 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffc900035bc944
Aug  4 09:18:19 iamserver kernel: RBP: ffffc900035bc944 R08: 000000000270ac88 R09: 0000000000000000
Aug  4 09:18:19 iamserver kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Aug  4 09:18:19 iamserver kernel: R13: 00000000ffffffff R14: 0000000000000001 R15: 0000000000000001
Aug  4 09:18:19 iamserver kernel: _raw_spin_lock+0x16/0x19
Aug  4 09:18:19 iamserver kernel: futex_wake+0x91/0x147
Aug  4 09:18:19 iamserver kernel: do_futex+0x20e/0x9dc
Aug  4 09:18:19 iamserver kernel: ? wake_up_q+0x2d/0x48
Aug  4 09:18:19 iamserver kernel: ? rwsem_wake+0x9b/0xbe
Aug  4 09:18:19 iamserver kernel: __se_sys_futex+0x131/0x156
Aug  4 09:18:19 iamserver kernel: ? __do_page_fault+0x36d/0x3ff
Aug  4 09:18:19 iamserver kernel: do_syscall_64+0x57/0xf2
Aug  4 09:18:19 iamserver kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug  4 09:18:19 iamserver kernel: RIP: 0033:0x45f623
Aug  4 09:18:19 iamserver kernel: Code: 24 20 c3 cc cc cc cc 48 8b 7c 24 08 8b 74 24 10 8b 54 24 14 4c 8b 54 24 18 4c 8b 44 24 20 44 8b 4c 24 28 b8 ca 00 00 00 0f 05 <89> 44 24 30 c3 cc cc cc cc cc cc cc cc 8b 7c 24 08 48 8b 74 24 10
Aug  4 09:18:19 iamserver kernel: RSP: 002b:000014e0d5f7ab98 EFLAGS: 00000206 ORIG_RAX: 00000000000000ca
Aug  4 09:18:19 iamserver kernel: RAX: ffffffffffffffda RBX: 000000c0004b9000 RCX: 000000000045f623
Aug  4 09:18:19 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000081 RDI: 000000000270ac88
Aug  4 09:18:19 iamserver kernel: RBP: 000014e0d5f7abe8 R08: 0000000000000000 R09: 0000000000000000
Aug  4 09:18:19 iamserver kernel: R10: 0000000000000000 R11: 0000000000000206 R12: ffffffffffffffff
Aug  4 09:18:19 iamserver kernel: R13: 0000000000000002 R14: 0000000000000001 R15: 0000000000000200

I started seeing them after installing this this Dell H310 6Gbps SAS HBA card, or after I started to use the 10GB port on my mobo

 

My server was a Ryzen 2700x in a ASRock x470 Tarichi Ultimate, but I decided to swap it with my desktop, a 6700k in a Gigabyte Gaming 7 x170 and popped in a SuperMicro X540-AT2 AOC-STG-I2T 10GB Ethernet card. Since then, I started to see:

Aug  8 15:43:44 iamserver kernel: ------------[ cut here ]------------
Aug  8 15:43:44 iamserver kernel: WARNING: CPU: 6 PID: 5707 at net/netfilter/nf_nat_core.c:420 nf_nat_setup_info+0x94/0x666 [nf_nat]
Aug  8 15:43:44 iamserver kernel: Modules linked in: veth nvidia_uvm(O) arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod e1000e ixgbe(O) alx mdio nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) crc32_pclmul intel_rapl_perf intel_uncore pcbc aesni_intel aes_x86_64 glue_helper crypto_simd ghash_clmulni_intel cryptd hid_logitech_hidpp kvm_intel intel_wmi_thunderbolt mxm_wmi kvm drm_kms_helper intel_cstate drm coretemp mpt3sas crct10dif_pclmul intel_powerclamp syscopyarea sysfillrect ahci crc32c_intel sysimgblt fb_sys_fops libahci raid_class x86_pkg_temp_thermal agpgart wmi hid_logitech_dj video scsi_transport_sas i2c_i801 i2c_core pcc_cpufreq backlight thermal button acpi_pad fan [last unloaded: e1000e]
Aug  8 15:43:44 iamserver kernel: CPU: 6 PID: 5707 Comm: kworker/6:0 Tainted: P           O      4.19.107-Unraid #1
Aug  8 15:43:44 iamserver kernel: Hardware name: Gigabyte Technology Co., Ltd. Z170X-Gaming 7/Z170X-Gaming 7, BIOS F22m 03/09/2018
Aug  8 15:43:44 iamserver kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Aug  8 15:43:44 iamserver kernel: RIP: 0010:nf_nat_setup_info+0x94/0x666 [nf_nat]
Aug  8 15:43:44 iamserver kernel: Code: 0d 8b 87 80 00 00 00 25 80 00 00 00 eb 0c 41 8b 86 80 00 00 00 25 00 01 00 00 85 c0 74 13 48 c7 c7 cc 51 0f a0 e8 8b a9 f9 e0 <0f> 0b e9 49 01 00 00 4c 8d 6c 24 30 49 8d 76 58 4c 89 ef e8 bd 10
Aug  8 15:43:44 iamserver kernel: RSP: 0018:ffff88883eb83c50 EFLAGS: 00010246
Aug  8 15:43:44 iamserver kernel: RAX: 0000000000000024 RBX: ffff88883eb83df0 RCX: 0000000000000000
Aug  8 15:43:44 iamserver kernel: RDX: 0000000000000000 RSI: ffff88883eb964f8 RDI: ffff88883eb964f8
Aug  8 15:43:44 iamserver kernel: RBP: ffff88883eb83d28 R08: 0000000000000003 R09: 000000000001fa00
Aug  8 15:43:44 iamserver kernel: R10: 0000000000000000 R11: 0000000000000044 R12: 0000000000000000
Aug  8 15:43:44 iamserver kernel: R13: 0000000000000000 R14: ffff88814dc18500 R15: ffff88883eb83d3c
Aug  8 15:43:44 iamserver kernel: FS:  0000000000000000(0000) GS:ffff88883eb80000(0000) knlGS:0000000000000000
Aug  8 15:43:44 iamserver kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug  8 15:43:44 iamserver kernel: CR2: 00001551bf8f0000 CR3: 0000000001e0a002 CR4: 00000000003606e0
Aug  8 15:43:44 iamserver kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug  8 15:43:44 iamserver kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug  8 15:43:44 iamserver kernel: Call Trace:
Aug  8 15:43:44 iamserver kernel: <IRQ>
Aug  8 15:43:44 iamserver kernel: nf_nat_alloc_null_binding+0x71/0x88 [nf_nat]
Aug  8 15:43:44 iamserver kernel: nf_nat_inet_fn+0x9f/0x1b9 [nf_nat]
Aug  8 15:43:44 iamserver kernel: nf_hook_slow+0x3a/0x90
Aug  8 15:43:44 iamserver kernel: ip_local_deliver+0xad/0xdc
Aug  8 15:43:44 iamserver kernel: ? ip_sublist_rcv_finish+0x54/0x54
Aug  8 15:43:44 iamserver kernel: ip_sabotage_in+0x38/0x3e
Aug  8 15:43:44 iamserver kernel: nf_hook_slow+0x3a/0x90
Aug  8 15:43:44 iamserver kernel: ip_rcv+0x8e/0xbe
Aug  8 15:43:44 iamserver kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1
Aug  8 15:43:44 iamserver kernel: __netif_receive_skb_one_core+0x53/0x6f
Aug  8 15:43:44 iamserver kernel: process_backlog+0x77/0x10e
Aug  8 15:43:44 iamserver kernel: net_rx_action+0x107/0x26c
Aug  8 15:43:44 iamserver kernel: __do_softirq+0xc9/0x1d7
Aug  8 15:43:44 iamserver kernel: do_softirq_own_stack+0x2a/0x40
Aug  8 15:43:44 iamserver kernel: </IRQ>
Aug  8 15:43:44 iamserver kernel: do_softirq+0x4d/0x5a
Aug  8 15:43:44 iamserver kernel: netif_rx_ni+0x1c/0x22
Aug  8 15:43:44 iamserver kernel: macvlan_broadcast+0x111/0x156 [macvlan]
Aug  8 15:43:44 iamserver kernel: ? __switch_to_asm+0x41/0x70
Aug  8 15:43:44 iamserver kernel: macvlan_process_broadcast+0xea/0x128 [macvlan]
Aug  8 15:43:44 iamserver kernel: process_one_work+0x16e/0x24f
Aug  8 15:43:44 iamserver kernel: worker_thread+0x1e2/0x2b8
Aug  8 15:43:44 iamserver kernel: ? rescuer_thread+0x2a7/0x2a7
Aug  8 15:43:44 iamserver kernel: kthread+0x10c/0x114
Aug  8 15:43:44 iamserver kernel: ? kthread_park+0x89/0x89
Aug  8 15:43:44 iamserver kernel: ret_from_fork+0x35/0x40
Aug  8 15:43:44 iamserver kernel: ---[ end trace db298b547ca99952 ]---

 

Should I be concerned about these errors?

 

iamserver-diagnostics-20200809-1337.zip

  • Community Expert

Macvlan call traces are usually the result of having dockers with a custom IP address:

 

  • Author

I do use static IP addresses on basically all my dockers, but never ran into this issue before. Would disabling the onboard NICs in the BIOS help? I'd like to keep everything on the same subnet for now.

  • 2 weeks later...
  • Author

By downing the ports on the other interfaces I was able to eliminate the macvlan interrupts, but I just had the server lock up.

 

The following is repeated within my server logs, so it was still operating enough to log the errors, but I couldn't access the server and it wouldn't respond to a keyboard either.

 

Aug 19 17:00:45 iamserver kernel: rcu: INFO: rcu_sched self-detected stall on CPU
Aug 19 17:00:45 iamserver kernel: rcu:  3-....: (30292899 ticks this GP) idle=c6e/1/0x4000000000000002 softirq=12738753/12738753 fqs=7528016
Aug 19 17:00:45 iamserver kernel: rcu:   (t=30300554 jiffies g=29023597 q=38364515)
Aug 19 17:00:45 iamserver kernel: NMI backtrace for cpu 3
Aug 19 17:00:45 iamserver kernel: CPU: 3 PID: 327 Comm: khugepaged Tainted: P      D W  O      4.19.107-Unraid #1
Aug 19 17:00:45 iamserver kernel: Hardware name: Gigabyte Technology Co., Ltd. Z170X-Gaming 7/Z170X-Gaming 7, BIOS F22m 03/09/2018
Aug 19 17:00:45 iamserver kernel: Call Trace:
Aug 19 17:00:45 iamserver kernel: <IRQ>
Aug 19 17:00:45 iamserver kernel: dump_stack+0x67/0x83
Aug 19 17:00:45 iamserver kernel: nmi_cpu_backtrace+0x71/0x83
Aug 19 17:00:45 iamserver kernel: ? lapic_can_unplug_cpu+0x97/0x97
Aug 19 17:00:45 iamserver kernel: nmi_trigger_cpumask_backtrace+0x57/0xd4
Aug 19 17:00:45 iamserver kernel: rcu_dump_cpu_stacks+0x8b/0xb4
Aug 19 17:00:45 iamserver kernel: rcu_check_callbacks+0x296/0x5a0
Aug 19 17:00:45 iamserver kernel: update_process_times+0x24/0x47
Aug 19 17:00:45 iamserver kernel: tick_sched_timer+0x36/0x64
Aug 19 17:00:45 iamserver kernel: __hrtimer_run_queues+0xb7/0x10b
Aug 19 17:00:45 iamserver kernel: ? tick_sched_handle.isra.0+0x2f/0x2f
Aug 19 17:00:45 iamserver kernel: hrtimer_interrupt+0xf4/0x20e
Aug 19 17:00:45 iamserver kernel: smp_apic_timer_interrupt+0x7b/0x93
Aug 19 17:00:45 iamserver kernel: apic_timer_interrupt+0xf/0x20
Aug 19 17:00:45 iamserver kernel: </IRQ>
Aug 19 17:00:45 iamserver kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6b/0x171
Aug 19 17:00:45 iamserver kernel: Code: 42 f0 8b 07 30 e4 09 c6 f7 c6 00 ff ff ff 74 0e 81 e6 00 ff 00 00 75 1a c6 47 01 00 eb 14 85 f6 74 0a 8b 07 84 c0 74 04 f3 90 <eb> f6 66 c7 07 01 00 c3 48 c7 c2 40 07 02 00 65 48 03 15 80 6a f8
Aug 19 17:00:45 iamserver kernel: RSP: 0018:ffffc90003b13958 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
Aug 19 17:00:45 iamserver kernel: RAX: 00000000000c0101 RBX: ffffc90003b139e0 RCX: 000ffffffffff000
Aug 19 17:00:45 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffea00063e6c28
Aug 19 17:00:45 iamserver kernel: RBP: ffffea0007aff3c0 R08: ffff888000000000 R09: ffffea0007aff400
Aug 19 17:00:45 iamserver kernel: R10: 0000000000000013 R11: 0000000000023eb8 R12: ffffea0007aff3c0
Aug 19 17:00:45 iamserver kernel: R13: ffff8887413e1540 R14: ffffea0007aff3c0 R15: ffff8884f6915a80
Aug 19 17:00:45 iamserver kernel: _raw_spin_lock+0x16/0x19
Aug 19 17:00:45 iamserver kernel: page_vma_mapped_walk+0x58d/0x693
Aug 19 17:00:45 iamserver kernel: try_to_unmap_one+0x114/0x70f
Aug 19 17:00:45 iamserver kernel: rmap_walk_anon+0x1ad/0x21c
Aug 19 17:00:45 iamserver kernel: ? __ClearPageMovable+0x6/0x6
Aug 19 17:00:45 iamserver kernel: try_to_unmap+0x9e/0xdf
Aug 19 17:00:45 iamserver kernel: ? page_remove_rmap+0x2d8/0x2d8
Aug 19 17:00:45 iamserver kernel: ? page_not_mapped+0xc/0xc
Aug 19 17:00:45 iamserver kernel: ? page_get_anon_vma+0x69/0x69
Aug 19 17:00:45 iamserver kernel: ? is_vma_temporary_stack+0x20/0x20
Aug 19 17:00:45 iamserver kernel: migrate_pages+0x525/0x87c
Aug 19 17:00:45 iamserver kernel: ? isolate_freepages_block+0x279/0x279
Aug 19 17:00:45 iamserver kernel: compact_zone+0x3af/0x59c
Aug 19 17:00:45 iamserver kernel: compact_zone_order+0x79/0x93
Aug 19 17:00:45 iamserver kernel: try_to_compact_pages+0xb5/0x14a
Aug 19 17:00:45 iamserver kernel: __alloc_pages_direct_compact+0x49/0xde
Aug 19 17:00:45 iamserver kernel: __alloc_pages_nodemask+0x30f/0xae1
Aug 19 17:00:45 iamserver kernel: ? __lru_cache_add+0x51/0x51
Aug 19 17:00:45 iamserver kernel: ? pagevec_lru_move_fn+0xaa/0xb9
Aug 19 17:00:45 iamserver kernel: khugepaged+0xa67/0x1829
Aug 19 17:00:45 iamserver kernel: ? wait_woken+0x6a/0x6a
Aug 19 17:00:45 iamserver kernel: ? collapse_shmem+0xacd/0xacd
Aug 19 17:00:45 iamserver kernel: kthread+0x10c/0x114
Aug 19 17:00:45 iamserver kernel: ? kthread_park+0x89/0x89
Aug 19 17:00:45 iamserver kernel: ret_from_fork+0x35/0x40

 

  • Community Expert

Try running the server as a basic NAS for a couple of days, boot in safe mode and disable all dockers/VMs, if it still crashes like that you likely have a hardware problem, if it doesn't start enabling services one by one.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.