Hi, I noticed the following errors in my syslog today. Anything I should be concerned about?

 

Nov 17 13:31:01 Tower kernel: ------------[ cut here ]------------
Nov 17 13:31:01 Tower kernel: WARNING: CPU: 0 PID: 28667 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e()
Nov 17 13:31:01 Tower kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net vhost macvtap macvlan iptable_mangle tun 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 x86_pkg_temp_thermal coretemp kvm_intel kvm ahci libahci e1000e i2c_i801 i2c_core ptp pps_core
Nov 17 13:31:01 Tower kernel: CPU: 0 PID: 28667 Comm: mono Tainted: G W 4.4.30-unRAID #2
Nov 17 13:31:01 Tower kernel: Hardware name: Dell Inc. PowerEdge T20/0VD5HY, BIOS A06 01/27/2015
Nov 17 13:31:01 Tower kernel: 0000000000000000 ffff880007ab3ee0 ffffffff8136f79f 0000000000000000
Nov 17 13:31:01 Tower kernel: 00000000000000ec ffff880007ab3f18 ffffffff8104a4ab ffffffff8105569b
Nov 17 13:31:01 Tower kernel: fffffffffffffdfe 000000000000c6fc 000000000000000d 000000000000a4e3
Nov 17 13:31:01 Tower kernel: Call Trace:
Nov 17 13:31:01 Tower kernel: [<ffffffff8136f79f>] dump_stack+0x61/0x7e
Nov 17 13:31:01 Tower kernel: [<ffffffff8104a4ab>] warn_slowpath_common+0x8f/0xa8
Nov 17 13:31:01 Tower kernel: [<ffffffff8105569b>] ? SyS_rt_sigsuspend+0x8f/0x9e
Nov 17 13:31:01 Tower kernel: [<ffffffff8104a568>] warn_slowpath_null+0x15/0x17
Nov 17 13:31:01 Tower kernel: [<ffffffff8105569b>] SyS_rt_sigsuspend+0x8f/0x9e
Nov 17 13:31:01 Tower kernel: [<ffffffff81629c2e>] entry_SYSCALL_64_fastpath+0x12/0x6d
Nov 17 13:31:01 Tower kernel: ---[ end trace ac2bb6c86430c5c1 ]---

 

Thanks

Those are always bad, so yes, something that needs troubleshooting.  It's a crash of something, not enough clues to say what in, but it appears to have crashed mono, so that's a starting point.  The module that crashes is often not at fault though, but may be.

 

Always include your diagnostics - please see Need help? Read me first!, and attach the diagnostics zip.

Thanks for the reply. Attached are the diagnostics.

First crash was at Nov 15 04:52:01, can't tell what it's working on, probably deep in the kernel.  Early, but you were doing something with the server around then.

 

Second crash was at Nov 17 13:31:01, involved mono which is used with NzbDrone.  I don't see any evidence you were working on the server then.

 

I'm sorry, I can't find any other clues.  I don't think I have seen similar with any other users.  The only advice I can give you - when you see one of these, I recommend rebooting when it's next convenient.  There's a small possibility that a newer kernel will work better, if you'd like to try a 6.3 release.

 

Minor issue, at boot time, you also had ATA exceptions for the PNY SSD.  The SSD and its SATA port claimed to be able to do 6.0 Gbps, but failed to when mounted.  Once it dropped the SATA link speed from 6.0 Gbps to 3.0 Gbps, there were no further issues.  Apparently something about the SSD or its connection does not support the faster speed.  Not a real problem.

 

You have the Mover and the CA auto-backup set to run simultaneously at 1am.  You may want to move one of them to a different time.

Thanks so much! I guess I'll keep an eye on the log for now and see if the errors keep happening.

I seem to be seeing the same thing in 6.2.4 where upon every reboot, I see:

 

Dec 12 19:16:18 Tower kernel: ------------[ cut here ]------------
Dec 12 19:16:18 Tower kernel: WARNING: CPU: 7 PID: 2135 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e()
Dec 12 19:16:18 Tower kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan 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 igb ptp pps_core fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm coretemp kvm_intel agpgart syscopyarea sysfillrect sysimgblt kvm fb_sys_fops mvsas fb i2c_i801 fbdev i2c_algo_bit libsas ahci i2c_core libahci scsi_transport_sas ipmi_si acpi_cpufreq [last unloaded: pps_core]
Dec 12 19:16:18 Tower kernel: CPU: 7 PID: 2135 Comm: Threadpool work Not tainted 4.4.30-unRAID #2
Dec 12 19:16:18 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C2750D4I, BIOS P2.80 12/04/2014
Dec 12 19:16:18 Tower kernel: 0000000000000000 ffff88044ba0fee0 ffffffff8136f79f 0000000000000000
Dec 12 19:16:18 Tower kernel: 00000000000000ec ffff88044ba0ff18 ffffffff8104a4ab ffffffff8105569b
Dec 12 19:16:18 Tower kernel: fffffffffffffdfe 000000000000d266 000000000000000d 000000000000a0c4
Dec 12 19:16:18 Tower kernel: Call Trace:
Dec 12 19:16:18 Tower kernel: [<ffffffff8136f79f>] dump_stack+0x61/0x7e
Dec 12 19:16:18 Tower kernel: [<ffffffff8104a4ab>] warn_slowpath_common+0x8f/0xa8
Dec 12 19:16:18 Tower kernel: [<ffffffff8105569b>] ? SyS_rt_sigsuspend+0x8f/0x9e
Dec 12 19:16:18 Tower kernel: [<ffffffff8104a568>] warn_slowpath_null+0x15/0x17
Dec 12 19:16:18 Tower kernel: [<ffffffff8105569b>] SyS_rt_sigsuspend+0x8f/0x9e
Dec 12 19:16:18 Tower kernel: [<ffffffff81629c2e>] entry_SYSCALL_64_fastpath+0x12/0x6d
Dec 12 19:16:18 Tower kernel: ---[ end trace 36a511110db2574a ]---

 

Things seem to be working okay, but it's always concerning to see something like that in the syslog.  Any ideas?  I can provide a full log if it will be of assistance.

I seem to be seeing the same thing in 6.2.4 where upon every reboot, I see:

...

Things seem to be working okay, but it's always concerning to see something like that in the syslog.  Any ideas?  I can provide a full log if it will be of assistance.

...

Always include your diagnostics - please see Need help? Read me first!, and attach the diagnostics zip.

Also, probably better to start a separate support thread, yours doesn't look the same, involves threadpool not mono, may be even deeper in the kernel (which means there may be nothing we can do).  And check for a newer motherboard BIOS, might help.

Ah, I didn't notice the component difference there...probably should have diffed it against the original.  Good advice on the BIOS...let me try that and if it keeps occurring I'll start a new thread with fill diags.  Thanks.