cari

Rumah  >  Soal Jawab  >  teks badan

linux - NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s。

这个主机只安装了kvm,目前安装一些虚拟机作为内部测试用,但是最近经常性出现这个日志,并且出现这种日志的时候poweroff命令也无效,只能强制重启;
之前在网上查找怀疑是电源CPU供电不足导致,后来换过电源同样出现这个问题,现在不确定是硬件问题还是软件问题了,求大神们指点下

Apr  6 17:08:13 docker kernel: [ 6007.309244] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:4074]
Apr  6 17:08:13 docker kernel: [ 6007.309810] Modules linked in: aufs vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables ppdev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic bridge i915_bpo stp llc intel_rapl intel_ips snd_hda_intel snd_hda_codec snd_hda_core x86_pkg_temp_thermal intel_powerclamp snd_hwdep kvm_intel hci_uart snd_pcm kvm mei_me mei snd_timer snd soundcore btbcm btqca ie31200_edac btintel serio_raw shpchp edac_core irqbypass acpi_als kfifo_buf parport_pc parport tpm_infineon bluetooth intel_lpss_acpi intel_lpss industrialio 8250_fintek mac_hid acpi_pad ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp sunrpc libiscsi_tcp libiscsi scsi_transport_iscsi coretemp autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 nouveau crct10dif_pclmul crc32_pclmul ghash_clmulni_intel mxm_wmi i2c_algo_bit aesni_intel ttm aes_x86_64 lrw gf128mul drm_kms_helper glue_helper ablk_helper cryptd syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm ahci mii libahci pinctrl_sunrisepoint i2c_hid wmi video pinctrl_intel hid fjes
Apr  6 17:08:13 docker kernel: [ 6007.309852] CPU: 0 PID: 4074 Comm: qemu-system-x86 Tainted: G             L  4.4.0-62-generic #83-Ubuntu
Apr  6 17:08:13 docker kernel: [ 6007.309853] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./X150M-PLUS WS-CF, BIOS F3 03/30/2016
Apr  6 17:08:13 docker kernel: [ 6007.309854] task: ffff8807c876e900 ti: ffff8806c1628000 task.ti: ffff8806c1628000
Apr  6 17:08:13 docker kernel: [ 6007.309855] RIP: 0010:[<ffffffff81104558>]  [<ffffffff81104558>] smp_call_function_single+0xd8/0x130
Apr  6 17:08:13 docker kernel: [ 6007.309859] RSP: 0018:ffff8806c162bae8  EFLAGS: 00000202
Apr  6 17:08:13 docker kernel: [ 6007.309860] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000
Apr  6 17:08:13 docker kernel: [ 6007.309861] RDX: 0000000000000001 RSI: 00000000000000fb RDI: 0000000000000286
Apr  6 17:08:13 docker kernel: [ 6007.309861] RBP: ffff8806c162bb30 R08: ffff8806c1628000 R09: 0000000000000000
Apr  6 17:08:13 docker kernel: [ 6007.309862] R10: 00000001001463fe R11: 0000000000000000 R12: ffffffffc084ed60
Apr  6 17:08:13 docker kernel: [ 6007.309863] R13: 0000000000000000 R14: ffff8807e31b7c00 R15: 0000000000000000
Apr  6 17:08:13 docker kernel: [ 6007.309863] FS:  00007f4ef4128700(0000) GS:ffff880866400000(0000) knlGS:0000000000000000
Apr  6 17:08:13 docker kernel: [ 6007.309864] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr  6 17:08:13 docker kernel: [ 6007.309865] CR2: 000008449304b000 CR3: 000000083c611000 CR4: 00000000003426f0
Apr  6 17:08:13 docker kernel: [ 6007.309865] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr  6 17:08:13 docker kernel: [ 6007.309866] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr  6 17:08:13 docker kernel: [ 6007.309866] Stack:
Apr  6 17:08:13 docker kernel: [ 6007.309867]  0000000000000087 ffff8806c162bb60 0000000000000000 ffffffffc084ed60
Apr  6 17:08:13 docker kernel: [ 6007.309868]  ffff88083c9f4510 0000000000000003 00000000f5c469c6 ffff88083c9f0000
Apr  6 17:08:13 docker kernel: [ 6007.309869]  0000000000000000 ffff8806c162bc50 ffffffffc084d660 00000000145334f6
Apr  6 17:08:13 docker kernel: [ 6007.309870] Call Trace:
Apr  6 17:08:13 docker kernel: [ 6007.309875]  [<ffffffffc084ed60>] ? hardware_enable+0x1a0/0x1a0 [kvm_intel]
Apr  6 17:08:13 docker kernel: [ 6007.309877]  [<ffffffffc084d660>] vmx_vcpu_load+0x200/0x2f0 [kvm_intel]
Apr  6 17:08:13 docker kernel: [ 6007.309878]  [<ffffffff810b5239>] ? update_curr+0x79/0x160
Apr  6 17:08:13 docker kernel: [ 6007.309879]  [<ffffffff810b72eb>] ? dequeue_entity+0x41b/0xa80
Apr  6 17:08:13 docker kernel: [ 6007.309890]  [<ffffffffc0746f7b>] kvm_arch_vcpu_load+0x3b/0x220 [kvm]
Apr  6 17:08:13 docker kernel: [ 6007.309895]  [<ffffffffc072f699>] kvm_sched_in+0x39/0x40 [kvm]
Apr  6 17:08:13 docker kernel: [ 6007.309897]  [<ffffffff810a9c86>] finish_task_switch+0x166/0x220
Apr  6 17:08:13 docker kernel: [ 6007.309899]  [<ffffffff81833e16>] __schedule+0x3b6/0xa30
Apr  6 17:08:13 docker kernel: [ 6007.309907]  [<ffffffffc0768ba8>] ? kvm_apic_has_interrupt+0x28/0xd0 [kvm]
Apr  6 17:08:13 docker kernel: [ 6007.309909]  [<ffffffff818344c5>] schedule+0x35/0x80
Apr  6 17:08:13 docker kernel: [ 6007.309913]  [<ffffffffc0730552>] kvm_vcpu_block+0x82/0x2e0 [kvm]
Apr  6 17:08:13 docker kernel: [ 6007.309915]  [<ffffffff810c41e0>] ? wake_atomic_t_function+0x60/0x60
Apr  6 17:08:13 docker kernel: [ 6007.309922]  [<ffffffffc074cc13>] kvm_arch_vcpu_ioctl_run+0x1b3/0x400 [kvm]
Apr  6 17:08:13 docker kernel: [ 6007.309927]  [<ffffffffc073352d>] kvm_vcpu_ioctl+0x33d/0x620 [kvm]
Apr  6 17:08:13 docker kernel: [ 6007.309929]  [<ffffffff812227af>] do_vfs_ioctl+0x29f/0x490
Apr  6 17:08:13 docker kernel: [ 6007.309935]  [<ffffffffc0740706>] ? kvm_on_user_return+0x66/0xa0 [kvm]
Apr  6 17:08:13 docker kernel: [ 6007.309937]  [<ffffffff8118af6b>] ? fire_user_return_notifiers+0x3b/0x50
Apr  6 17:08:13 docker kernel: [ 6007.309938]  [<ffffffff81222a19>] SyS_ioctl+0x79/0x90
Apr  6 17:08:13 docker kernel: [ 6007.309940]  [<ffffffff818385f2>] entry_SYSCALL_64_fastpath+0x16/0x71
Apr  6 17:08:13 docker kernel: [ 6007.309940] Code: 25 28 00 00 00 75 70 48 83 c4 38 5b 41 5c 5d c3 48 8d 75 c8 48 89 d1 89 df 4c 89 e2 e8 12 fe ff ff 8b 55 e0 83 e2 01 74 cf f3 90 <8b> 55 e0 83 e2 01 75 f6 eb c3 8b 05 30 81 00 01 85 c0 75 85 80
Apr  6 17:08:14 docker kernel: [ 6008.221135] INFO: rcu_bh detected stalls on CPUs/tasks:
Apr  6 17:08:14 docker kernel: [ 6008.221737]     2-...: (1 GPs behind) idle=ffb/1/0 softirq=56650/56737 fqs=104452
Apr  6 17:08:14 docker kernel: [ 6008.222241]     (detected by 6, t=105012 jiffies, g=99, c=98, q=13)
Apr  6 17:08:14 docker kernel: [ 6008.222755] Task dump for CPU 2:
Apr  6 17:08:14 docker kernel: [ 6008.222757] swapper/2       R  running task        0     0      1 0x00000008
Apr  6 17:08:14 docker kernel: [ 6008.222759]  ffff880842133e70 0000000000000018 0000000066493bc0 000004de44ef6138
Apr  6 17:08:14 docker kernel: [ 6008.222760]  ffffffff81f38200 ffff880842134000 ffff88086649ec00 ffffffff81eb3120
Apr  6 17:08:14 docker kernel: [ 6008.222761]  ffff880842130000 ffff880842133eb8 ffffffff816cb7a7 ffff880842133ed0
Apr  6 17:08:14 docker kernel: [ 6008.222763] Call Trace:
Apr  6 17:08:14 docker kernel: [ 6008.222768]  [<ffffffff816cb7a7>] ? cpuidle_enter+0x17/0x20
Apr  6 17:08:14 docker kernel: [ 6008.222770]  [<ffffffff810c4522>] ? call_cpuidle+0x32/0x60
Apr  6 17:08:14 docker kernel: [ 6008.222771]  [<ffffffff816cb783>] ? cpuidle_select+0x13/0x20
Apr  6 17:08:14 docker kernel: [ 6008.222773]  [<ffffffff810c47e0>] ? cpu_startup_entry+0x290/0x350
Apr  6 17:08:14 docker kernel: [ 6008.222775]  [<ffffffff81051784>] ? start_secondary+0x154/0x190
PHP中文网PHP中文网2779 hari yang lalu3128

membalas semua(0)saya akan balas

Tiada jawapan
  • Batalbalas