had these in my logs 2 days in a row, not sure what it's saying. not sure if this is a software issue or hardware? i saw this thread: https://lime-technology.com/forum/index.php?topic=52070.0 however i don't have nerd tools installed anymore. everything appears to be working fine..

 

Nov 18 18:09:04 Tower kernel: ------------[ cut here ]------------
Nov 18 18:09:04 Tower kernel: WARNING: CPU: 3 PID: 27126 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e()
Nov 18 18:09:04 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod mvsas k10temp libsas kvm_amd sata_sil pata_atiixp kvm i2c_piix4 r8169 i2c_core mii ahci scsi_transport_sas libahci sata_sil24 wmi asus_atk0110 acpi_cpufreq
Nov 18 18:09:04 Tower kernel: CPU: 3 PID: 27126 Comm: mono Tainted: G    B   W       4.4.30-unRAID #2
Nov 18 18:09:04 Tower kernel: Hardware name: System manufacturer System Product Name/M4A88T-M, BIOS 2403    12/23/2010
Nov 18 18:09:04 Tower kernel: 0000000000000000 ffff880124037ee0 ffffffff8136f79f 0000000000000000
Nov 18 18:09:04 Tower kernel: 00000000000000ec ffff880124037f18 ffffffff8104a4ab ffffffff8105569b
Nov 18 18:09:04 Tower kernel: fffffffffffffdfe 000000000001481b 0000000000000002 00002b78c9cbef38
Nov 18 18:09:04 Tower kernel: Call Trace:
Nov 18 18:09:04 Tower kernel: [<ffffffff8136f79f>] dump_stack+0x61/0x7e
Nov 18 18:09:04 Tower kernel: [<ffffffff8104a4ab>] warn_slowpath_common+0x8f/0xa8
Nov 18 18:09:04 Tower kernel: [<ffffffff8105569b>] ? SyS_rt_sigsuspend+0x8f/0x9e
Nov 18 18:09:04 Tower kernel: [<ffffffff8104a568>] warn_slowpath_null+0x15/0x17
Nov 18 18:09:04 Tower kernel: [<ffffffff8105569b>] SyS_rt_sigsuspend+0x8f/0x9e
Nov 18 18:09:04 Tower kernel: [<ffffffff81629c2e>] entry_SYSCALL_64_fastpath+0x12/0x6d
Nov 18 18:09:04 Tower kernel: ---[ end trace 2a89d16674f70305 ]---

tower-diagnostics-20161119-0059.zip

Yours is now the third report with similar, search "mono tainted cut here".

 

Somewhere, there was a request to have mono updated, as the plugin or Docker was loading a rather old version.  Perhaps a newer version of mono would help?

so this is just a software issue, not anything hw related? if everything is still working is there any huge concern?

We can't say for sure, but it does look like a software issue.  It's a form of crash, so we can't say everything is working, even if you can't detect anything wrong.  Something isn't right, and that is a concern, but there's nothing that I can see yet as to whether it's a small or huge concern.

What is mono? All I can find by Googling is a reference to an open source implementation of Microsoft's .NET framework. Is it used by core unRAID or is it installed by a plugin?

 

What is mono? All I can find by Googling is a reference to an open source implementation of Microsoft's .NET framework. Is it used by core unRAID or is it installed by a plugin?

 

i think it's a plugin. i know for sure nzbdrone/sonarr uses mono, not sure which others do. is there any way to check which version of mono i have and which docker uses it?

Ah. I don't use either of those. If it's a plugin that uses it it will be loaded at boot time, along with the plugin, so it ought to show up in your syslog. If it's a docker that uses it, then I don't know how you find out the details.