I was taking a look at my syslog when I noticed a call trace inside it. Can anyone tell me if this call trace is something to worry about? Logs attached.

 

System is still up in case anything else needs to be looked at / pulled.

 

This call trace happened during a parity check:

 

Last check completed on Tue 02 Oct 2018 12:23:27 AM PDT (today), finding 0 errors. 
Duration: 1 day, 23 minutes, 26 seconds. Average speed: 91.1 MB/sec

 

Oct 1 14:16:45 Smalls kernel: Call Trace:
Oct 1 14:16:45 Smalls kernel: <IRQ>
Oct 1 14:16:45 Smalls kernel: dump_stack+0x5d/0x79
Oct 1 14:16:45 Smalls kernel: nmi_cpu_backtrace+0x71/0x83
Oct 1 14:16:45 Smalls kernel: ? lapic_can_unplug_cpu+0x8e/0x8e
Oct 1 14:16:45 Smalls kernel: nmi_trigger_cpumask_backtrace+0x57/0xd7
Oct 1 14:16:45 Smalls kernel: rcu_dump_cpu_stacks+0x91/0xbb
Oct 1 14:16:45 Smalls kernel: rcu_check_callbacks+0x23f/0x5ca
Oct 1 14:16:45 Smalls kernel: ? tick_sched_handle.isra.5+0x2f/0x2f
Oct 1 14:16:45 Smalls kernel: update_process_times+0x23/0x45
Oct 1 14:16:45 Smalls kernel: tick_sched_timer+0x36/0x64
Oct 1 14:16:45 Smalls kernel: __hrtimer_run_queues+0xb1/0x105
Oct 1 14:16:45 Smalls kernel: hrtimer_interrupt+0xf4/0x20d
Oct 1 14:16:45 Smalls kernel: smp_apic_timer_interrupt+0x79/0x89
Oct 1 14:16:45 Smalls kernel: apic_timer_interrupt+0xf/0x20
Oct 1 14:16:45 Smalls kernel: </IRQ>
Oct 1 14:16:45 Smalls kernel: RIP: 0010:memcmp+0xb/0x1d
Oct 1 14:16:45 Smalls kernel: Code: 3c c1 48 85 ff 74 10 4c 89 d6 e8 74 ff ff ff 84 c0 75 09 ff c1 eb df b9 ea ff ff ff 89 c8 c3 31 c9 48 39 d1 74 13 0f b6 04 0f <44> 0f b6 04 0e 48 ff c1 44 29 c0 74 ea eb 02 31 c0 c3 48 01 fa 48 
Oct 1 14:16:45 Smalls kernel: RSP: 0018:ffffc900078e3cb0 EFLAGS: 00000287 ORIG_RAX: ffffffffffffff13
Oct 1 14:16:45 Smalls kernel: RAX: 00000000000000d2 RBX: ffff88101add6ac0 RCX: 0000000000000000
Oct 1 14:16:45 Smalls kernel: RDX: 0000000000001000 RSI: ffff881038527000 RDI: ffff88101ae4a000
Oct 1 14:16:45 Smalls kernel: RBP: ffff881016b57800 R08: 0000000000000065 R09: ffff88101ae49000
Oct 1 14:16:45 Smalls kernel: R10: 0000000000000fd0 R11: 0000000000000ff0 R12: 0000000000000001
Oct 1 14:16:45 Smalls kernel: R13: ffff88101ae4a000 R14: ffff88101ae49000 R15: 0000000000000012
Oct 1 14:16:45 Smalls kernel: check_parity+0x2a7/0x349 [md_mod]
Oct 1 14:16:45 Smalls kernel: ? autoremove_wake_function+0x9/0x2a
Oct 1 14:16:45 Smalls kernel: ? __wake_up_common+0xa5/0x121
Oct 1 14:16:45 Smalls kernel: handle_stripe+0xe8a/0x1226 [md_mod]
Oct 1 14:16:45 Smalls kernel: unraidd+0xbc/0x123 [md_mod]
Oct 1 14:16:45 Smalls kernel: ? md_open+0x2c/0x2c [md_mod]
Oct 1 14:16:45 Smalls kernel: md_thread+0xcc/0xf1 [md_mod]
Oct 1 14:16:45 Smalls kernel: ? wait_woken+0x68/0x68
Oct 1 14:16:45 Smalls kernel: kthread+0x10b/0x113
Oct 1 14:16:45 Smalls kernel: ? kthread_flush_work_fn+0x9/0x9
Oct 1 14:16:45 Smalls kernel: ret_from_fork+0x35/0x40

 

smalls-diagnostics-20181001-2011.zip

Edited October 2, 20187 yr by GroxyPod

You got an NMI during parity check, it's happening to some users on latest releases, just one shouldn't be a cause for concern, but if it gets worse lowering the tunables usually alleviates the problem.

10 minutes ago, johnnie.black said:

You got an NMI during parity check, it's happening to some users on latest releases, just one shouldn't be a cause for concern, but if it gets worse lowering the tunables usually alleviates the problem.

 

Thanks for the reply johnnie.black, as always!

 

Aside from the sluggish parity check, the only other issues I ran into were Plex buffering (both internal and external). I did have CPU Pinning enabled, and have since disabled it for testing purposes.

 

Would the tunables test script still apply for v6.6.1, or is there a different method to use?

 

4 minutes ago, GroxyPod said:

Would the tunables test script still apply for v6.6.1, or is there a different method to use?

The script isn't compatible with Unraid since v6.2, also it generally would raise the values, not what you want, just decrease all 3 tunables by 5 or 10 percent.

The script isn't compatible with Unraid since v6.2, also it generally would raise the values, not what you want, just decrease all 3 tunables by 5 or 10 percent.

Sounds good. If I run into issues I will do the 5-10 percent method. Thanks again!


Sent from my iPhone using Tapatalk Pro