F4-220 unreachable

[Giuvash]

Hi all, tonight my F4-220 became unreachable during a data transfer from my F5-221.
i bought an used F4 ti install it as backup for the important data of the F5.
The F4 finished to sync array aroud 10 PM and after i started copy files.
This mornig i found the F4 switched on but ping, web gui and ssh was KO. NO red led.
I restarted the nas and now is up and running.
I find this repeatedly in the messages log:

Apr 7 14:41:36 TNAS-Backup kernel: Code: ff 56 48 41 89 c5 e8 75 e5 3c ff 65 8b 3d fe 00 13 6c e8 e9 e3 3c ff 31 ff 49 89 c4 e8 8f ed 3c ff 45 84 ff 75 64 fb 4c 89 e1 <48> 2b 4d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 c8 48 c1 f9 3f 48
Apr 7 14:41:36 TNAS-Backup kernel: RSP: 0018:ffffb36c4038be58 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffd9
Apr 7 14:41:36 TNAS-Backup kernel: RAX: ffff8bc7f6f1eb40 RBX: ffff8bc7f6f27ee8 RCX: 0000047f28751666
Apr 7 14:41:36 TNAS-Backup kernel: RDX: 0000047f28751666 RSI: 0000000034fc9927 RDI: 0000000000000000
Apr 7 14:41:36 TNAS-Backup kernel: RBP: ffffb36c4038be90 R08: 0000000000000002 R09: 000000000001e400
Apr 7 14:41:36 TNAS-Backup kernel: R10: ffffb36c4038be38 R11: 0000000000000000 R12: 0000047f28751666
Apr 7 14:41:36 TNAS-Backup kernel: R13: 0000000000000001 R14: ffffffff94e70d98 R15: 0000000000000000
Apr 7 14:41:36 TNAS-Backup kernel: ? cpuidle_enter_state+0x111/0x1b0
Apr 7 14:41:36 TNAS-Backup kernel: cpuidle_enter+0x12/0x20
Apr 7 14:41:36 TNAS-Backup kernel: call_cpuidle+0x1e/0x30
Apr 7 14:41:36 TNAS-Backup kernel: do_idle+0x1da/0x230
Apr 7 14:41:36 TNAS-Backup kernel: cpu_startup_entry+0x6e/0x70
Apr 7 14:41:36 TNAS-Backup kernel: start_secondary+0x169/0x1a0
Apr 7 14:41:36 TNAS-Backup kernel: secondary_startup_64+0xa4/0xb0
Apr 7 14:41:36 TNAS-Backup kernel: swapper/1: page allocation failure: order:0, mode:0x480020(GFP_ATOMIC), nodemask=(null)
Apr 7 14:41:36 TNAS-Backup kernel: swapper/1 cpuset=/ mems_allowed=0
Apr 7 14:41:36 TNAS-Backup kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: G O 4.19.165+ #435
Apr 7 14:41:36 TNAS-Backup kernel: Hardware name: retsamarret To be filled by O.E.M./Aptio CRB, BIOS 5.6.5 08/16/2016
Apr 7 14:41:36 TNAS-Backup kernel: Call Trace:
Apr 7 14:41:36 TNAS-Backup kernel: <IRQ>
Apr 7 14:41:36 TNAS-Backup kernel: dump_stack+0x57/0x75
Apr 7 14:41:36 TNAS-Backup kernel: warn_alloc+0xf7/0x180
Apr 7 14:41:36 TNAS-Backup kernel: __alloc_pages_slowpath+0xc02/0xc40
Apr 7 14:41:36 TNAS-Backup kernel: ? ip_rcv_finish+0x76/0x90
Apr 7 14:41:36 TNAS-Backup kernel: __alloc_pages_nodemask+0x20b/0x230
Apr 7 14:41:36 TNAS-Backup kernel: page_frag_alloc+0x150/0x190
Apr 7 14:41:36 TNAS-Backup kernel: __napi_alloc_skb+0x8a/0xe0
Apr 7 14:41:36 TNAS-Backup kernel: rtl8169_poll+0x15f/0x640
Apr 7 14:41:36 TNAS-Backup kernel: net_rx_action+0x120/0x320
Apr 7 14:41:36 TNAS-Backup kernel: __do_softirq+0xc4/0x211
Apr 7 14:41:36 TNAS-Backup kernel: irq_exit+0xba/0xc0
Apr 7 14:41:36 TNAS-Backup kernel: do_IRQ+0x73/0xd0
Apr 7 14:41:36 TNAS-Backup kernel: common_interrupt+0xf/0xf
Apr 7 14:41:36 TNAS-Backup kernel: </IRQ>
Apr 7 14:41:36 TNAS-Backup kernel: RIP: 0010:cpuidle_enter_state+0x11a/0x1b0


there are log to understand if F4 has hardware problems?
I have until tomorrow to return it
Thanks

[Giuvash]

system date obviously is wrong, i will adjust it

[TMRyan]

Looks like there's a problem with the memory, the memory is not enough, is your memory third-party memory or long used memory?

[Giuvash]

Seller sent me a wrong power adapter.. resolved. thanks!