Because i have no idea

 

Very few clues there, but it's a crash, at a very low level.  Since it occurred over 2 days ago, without any other apparent consequences, you seemed to have survived it.  I don't recognize it myself, I don't think it's a common issue.  All I can recommend is check for a newer motherboard BIOS.

Hmm interesting.. i never would have even seen it if i hadn't looked in there to see what the first file integrity scan looked like in the log. Pretty sure the BIOS is up to date as of last year. Been running this bored as my main PC until i decided to use it for unRAID. I dont really feel like rebooting the server to find out ATM *shrugs* hehe

http://www.gossamer-threads.com/lists/linux/kernel/2357559

fix apparently went into 4.5:

http://marc.info/?l=linux-kernel&m=145373718522970&w=2

 

If you run unRAID 6.3.0-rc1 you should not see this, but I think this is harmless.

Well that was all well over my head. lol

 

If you think it's harmless should i just ignore?

 

EDIT: Just happened again in the log. Also, BIOS is newest.

 

Oct 15 12:13:02 unDERP kernel: ------------[ cut here ]------------
Oct 15 12:13:02 unDERP kernel: WARNING: CPU: 3 PID: 6811 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e()
Oct 15 12:13:02 unDERP kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod nct6775 hwmon_vid mxm_wmi x86_pkg_temp_thermal coretemp kvm_intel r8169 i2c_i801 i2c_core kvm ahci libahci mii wmi
Oct 15 12:13:02 unDERP kernel: CPU: 3 PID: 6811 Comm: Threadpool work Tainted: G W 4.4.19-unRAID #1
Oct 15 12:13:02 unDERP kernel: Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.9 05/30/2015
Oct 15 12:13:02 unDERP kernel: 0000000000000000 ffff88002f507ee0 ffffffff8136a68e 0000000000000000
Oct 15 12:13:02 unDERP kernel: 00000000000000ec ffff88002f507f18 ffffffff8104a39a ffffffff81055502
Oct 15 12:13:02 unDERP kernel: fffffffffffffdfe 00000000000293cc 0000000000000002 0000000000000001
Oct 15 12:13:02 unDERP kernel: Call Trace:
Oct 15 12:13:02 unDERP kernel: [<ffffffff8136a68e>] dump_stack+0x61/0x7e
Oct 15 12:13:02 unDERP kernel: [<ffffffff8104a39a>] warn_slowpath_common+0x8f/0xa8
Oct 15 12:13:02 unDERP kernel: [<ffffffff81055502>] ? SyS_rt_sigsuspend+0x8f/0x9e
Oct 15 12:13:02 unDERP kernel: [<ffffffff8104a457>] warn_slowpath_null+0x15/0x17
Oct 15 12:13:02 unDERP kernel: [<ffffffff81055502>] SyS_rt_sigsuspend+0x8f/0x9e
Oct 15 12:13:02 unDERP kernel: [<ffffffff81620a2e>] entry_SYSCALL_64_fastpath+0x12/0x6d
Oct 15 12:13:02 unDERP kernel: ---[ end trace 4ea8c973756422e6 ]---

 

 

If you think it's harmless should i just ignore?

No one can say for sure, but it looks harmless.  What he is saying is that the kernel in the 6.3 series should have the fix, so if you are willing to try the 6.3 release, you should not see the problem again.

Alright, thanks. I guess i will just wait till 6.3 isn't rc since i don't really notice anything unless i look in the log.

 

Unless this could be causing networking problems. That is the only problem im having with unRAID (basically whenever i connect my laptop to my network unRAID's and only unRAID's, connection goes up and down every few seconds. Sometime for hours). But it doesn't seem related.