Jump to content

Kernel Errors in Syslog


Recommended Posts

The following kernel errors just showed up in my syslog (note:  I am currently running preclear on two 3TB WD Red drives - the preclear on both continues to run with no problems):

 

Nov  4 20:33:20 MediaNAS kernel: ------------[ cut here ]------------
Nov  4 20:33:20 MediaNAS kernel: WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x2f/0xb9()
Nov  4 20:33:20 MediaNAS kernel: Hardware name: TH61 ITX
Nov  4 20:33:20 MediaNAS kernel: empty IPI mask
Nov  4 20:33:20 MediaNAS kernel: Modules linked in: md_mod xor sg r8168(O) ahci libahci sata_mv coretemp hwmon i2c_i801 i2c_core mperf [last unloaded: md_mod]
Nov  4 20:33:20 MediaNAS kernel: Pid: 26241, comm: flush-8:64 Tainted: G           O 3.4.4-unRAID #2
Nov  4 20:33:20 MediaNAS kernel: Call Trace:
Nov  4 20:33:20 MediaNAS kernel:  [] warn_slowpath_common+0x65/0x7a
Nov  4 20:33:20 MediaNAS kernel:  [] ? default_send_IPI_mask_logical+0x2f/0xb9
Nov  4 20:33:20 MediaNAS kernel:  [] warn_slowpath_fmt+0x26/0x2a
Nov  4 20:33:20 MediaNAS kernel:  [] default_send_IPI_mask_logical+0x2f/0xb9
Nov  4 20:33:20 MediaNAS kernel:  [] native_send_call_func_ipi+0x4c/0x4e
Nov  4 20:33:20 MediaNAS kernel:  [] smp_call_function_many+0x18c/0x1a4
Nov  4 20:33:20 MediaNAS kernel:  [] ? page_alloc_cpu_notify+0x34/0x34
Nov  4 20:33:20 MediaNAS kernel:  [] ? page_alloc_cpu_notify+0x34/0x34
Nov  4 20:33:20 MediaNAS kernel:  [] on_each_cpu_mask+0x24/0x3f
Nov  4 20:33:20 MediaNAS kernel:  [] drain_all_pages+0x6f/0x80
Nov  4 20:33:20 MediaNAS kernel:  [] __alloc_pages_nodemask+0x370/0x4a5
Nov  4 20:33:20 MediaNAS kernel:  [] allocate_slab+0x3c/0xbc
Nov  4 20:33:20 MediaNAS kernel:  [] new_slab+0x22/0xeb
Nov  4 20:33:20 MediaNAS kernel:  [] T.1697+0x170/0x231
Nov  4 20:33:20 MediaNAS kernel:  [] ? mempool_alloc_slab+0xe/0x10
Nov  4 20:33:20 MediaNAS kernel:  [] ? blk_recount_segments+0x16/0x24
Nov  4 20:33:20 MediaNAS kernel:  [] kmem_cache_alloc+0x37/0x84
Nov  4 20:33:20 MediaNAS kernel:  [] ? kmem_cache_alloc+0x37/0x84
Nov  4 20:33:20 MediaNAS kernel:  [] ? mempool_alloc_slab+0xe/0x10
Nov  4 20:33:20 MediaNAS kernel:  [] mempool_alloc_slab+0xe/0x10
Nov  4 20:33:20 MediaNAS kernel:  [] mempool_alloc+0x37/0xec
Nov  4 20:33:20 MediaNAS kernel:  [] ? generic_make_request+0x7b/0xb0
Nov  4 20:33:20 MediaNAS kernel:  [] bio_alloc_bioset+0x24/0x94
Nov  4 20:33:20 MediaNAS kernel:  [] bio_alloc+0xe/0x1b
Nov  4 20:33:20 MediaNAS kernel:  [] submit_bh+0x68/0x102
Nov  4 20:33:20 MediaNAS kernel:  [] __block_write_full_page+0x215/0x2e0
Nov  4 20:33:20 MediaNAS kernel:  [] ? blkdev_get_blocks+0x93/0x93
Nov  4 20:33:20 MediaNAS kernel:  [] block_write_full_page_endio+0xa0/0xaa
Nov  4 20:33:20 MediaNAS kernel:  [] ? end_buffer_async_read+0xd1/0xd1
Nov  4 20:33:20 MediaNAS kernel:  [] ? blkdev_get_blocks+0x93/0x93
Nov  4 20:33:20 MediaNAS kernel:  [] block_write_full_page+0xd/0xf
Nov  4 20:33:20 MediaNAS kernel:  [] ? end_buffer_async_read+0xd1/0xd1
Nov  4 20:33:20 MediaNAS kernel:  [] blkdev_writepage+0xf/0x11
Nov  4 20:33:20 MediaNAS kernel:  [] __writepage+0xb/0x23
Nov  4 20:33:20 MediaNAS kernel:  [] write_cache_pages+0x199/0x26a
Nov  4 20:33:20 MediaNAS kernel:  [] ? set_page_dirty+0x59/0x59
Nov  4 20:33:20 MediaNAS kernel:  [] generic_writepages+0x32/0x46
Nov  4 20:33:20 MediaNAS kernel:  [] do_writepages+0x17/0x24
Nov  4 20:33:20 MediaNAS kernel:  [] writeback_single_inode+0xea/0x239
Nov  4 20:33:20 MediaNAS kernel:  [] writeback_sb_inodes+0x12d/0x1a3
Nov  4 20:33:20 MediaNAS kernel:  [] __writeback_inodes_wb+0x57/0x88
Nov  4 20:33:20 MediaNAS kernel:  [] wb_writeback+0xcb/0x12c
Nov  4 20:33:20 MediaNAS kernel:  [] wb_do_writeback+0x147/0x15f
Nov  4 20:33:20 MediaNAS kernel:  [] bdi_writeback_thread+0x6b/0x10e
Nov  4 20:33:20 MediaNAS kernel:  [] ? wb_do_writeback+0x15f/0x15f
Nov  4 20:33:20 MediaNAS kernel:  [] kthread+0x67/0x6c
Nov  4 20:33:20 MediaNAS kernel:  [] ? kthread_freezable_should_stop+0x49/0x49
Nov  4 20:33:20 MediaNAS kernel:  [] kernel_thread_helper+0x6/0xd
Nov  4 20:33:20 MediaNAS kernel: ---[ end trace 66e93fb46684d3e2 ]---

 

Are these errors cause for concern at this point?  To my knowledge, these errors have never before appeared in the syslog.  They look CPU cache related.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...