July 6, 20178 yr Hi, My server has been crashing a bit recently - maybe once a week. There seem to be a lot of these errors in the syslog: Jul 6 14:48:27 nas kernel: CPU: 0 PID: 8477 Comm: CPU 0/KVM Tainted: G W 4.9.30-unRAID #1 And the call trace looks like below. One of my VMs? Jul 6 14:48:27 nas kernel: Call Trace: Jul 6 14:48:27 nas kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Jul 6 14:48:27 nas kernel: [<ffffffff810cb5b1>] warn_alloc+0x102/0x116 Jul 6 14:48:27 nas kernel: [<ffffffff810cc07f>] __alloc_pages_nodemask+0xa59/0xc71 Jul 6 14:48:27 nas kernel: [<ffffffff81108678>] kmalloc_large_node+0x54/0x82 Jul 6 14:48:27 nas kernel: [<ffffffff8110b1be>] __kmalloc_node+0x22/0x132 Jul 6 14:48:27 nas kernel: [<ffffffff8100c8f6>] reserve_ds_buffers+0x192/0x353 Jul 6 14:48:27 nas kernel: [<ffffffff8100460f>] x86_reserve_hardware+0x135/0x147 Jul 6 14:48:27 nas kernel: [<ffffffff81004671>] x86_pmu_event_init+0x50/0x1c9 Jul 6 14:48:27 nas kernel: [<ffffffff810b8208>] perf_try_init_event+0x41/0x72 Jul 6 14:48:27 nas kernel: [<ffffffff810b8af3>] perf_event_alloc+0x482/0x7ca Jul 6 14:48:27 nas kernel: [<ffffffffa0182ec7>] ? reprogram_counter+0x54/0x54 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffff810ba776>] perf_event_create_kernel_counter+0x24/0x120 Jul 6 14:48:27 nas kernel: [<ffffffffa0182c10>] pmc_reprogram_counter+0xbf/0x104 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa0182d7e>] reprogram_gp_counter+0x129/0x146 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa0182ea6>] reprogram_counter+0x33/0x54 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa030c1fd>] intel_pmu_set_msr+0x16a/0x2ca [kvm_intel] Jul 6 14:48:27 nas kernel: [<ffffffffa01830c6>] kvm_pmu_set_msr+0x15/0x17 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa0163eb2>] kvm_set_msr_common+0x9d2/0xa64 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa030b58b>] vmx_set_msr+0x3cc/0x3de [kvm_intel] Jul 6 14:48:27 nas kernel: [<ffffffffa0160741>] kvm_set_msr+0x61/0x63 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa03041e9>] handle_wrmsr+0x3b/0x62 [kvm_intel] Jul 6 14:48:27 nas kernel: [<ffffffffa030b055>] vmx_handle_exit+0xf9d/0x1035 [kvm_intel] Jul 6 14:48:27 nas kernel: [<ffffffffa016a8a9>] kvm_arch_vcpu_ioctl_run+0x357/0x1165 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa0302f4c>] ? __vmx_load_host_state.part.27+0x120/0x127 [kvm_intel] Jul 6 14:48:27 nas kernel: [<ffffffffa0165088>] ? kvm_arch_vcpu_load+0xea/0x1a0 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffffa015ad71>] kvm_vcpu_ioctl+0x178/0x499 [kvm] Jul 6 14:48:27 nas kernel: [<ffffffff810b4c8f>] ? perf_ctx_unlock+0x1f/0x22 Jul 6 14:48:27 nas kernel: [<ffffffff810bd85b>] ? __perf_event_task_sched_in+0xd0/0x135 Jul 6 14:48:27 nas kernel: [<ffffffff81130112>] vfs_ioctl+0x13/0x2f Jul 6 14:48:27 nas kernel: [<ffffffff81130642>] do_vfs_ioctl+0x49c/0x50a Jul 6 14:48:27 nas kernel: [<ffffffff8113921f>] ? __fget+0x72/0x7e Jul 6 14:48:27 nas kernel: [<ffffffff811306ee>] SyS_ioctl+0x3e/0x5c Jul 6 14:48:27 nas kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9 nas-diagnostics-20170706-1453.zip
Archived
This topic is now archived and is closed to further replies.