偶尔的dmesg日志“ NOHZ:local_softirq_pending 08”


6

我有一个Ubuntu 14.04服务器,有时会向dmesg日志发出“ NOHZ:local_softirq_pending 08”错误。这是在升级到内核4.4之后开始的。以前,它在3.16内核上运行没有问题。这是日志结尾的摘录:

[    7.805258] audit: type=1400 audit(1484883362.092:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1636 comm="apparmor_parser"
[   10.605443] igb 0000:c1:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   10.605545] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   19.219187] ixgbe 0000:02:00.1 p4p2: NIC Link is Up 10 Gbps, Flow Control: None
[   19.219368] IPv6: ADDRCONF(NETDEV_CHANGE): p4p2: link becomes ready
[   52.010390] ip_tables: (C) 2000-2006 Netfilter Core Team
[   52.089283] init: plymouth-upstart-bridge main process ended, respawning
[ 2857.027773] perf interrupt took too long (2542 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 7195.391731] perf interrupt took too long (5012 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
[37277.461862] perf interrupt took too long (10050 > 10000), lowering kernel.perf_event_max_sample_rate to 12500
[239795.500056] NOHZ: local_softirq_pending 08
[579047.644110] NOHZ: local_softirq_pending 08
[837865.916051] NOHZ: local_softirq_pending 08

这是一个具有32个核心的生产数据库主机,负载相当大。

我想知道我是否应该关注这些消息,如果可以的话,我应该如何解决该问题。

内核详细信息在这里:

[    0.000000] Linux version 4.4.0-59-generic (buildd@lcy01-32) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #80~14.04.1-Ubuntu SMP Fri Jan 6 18:02:02 UTC 2017 (Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35)
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=UUID=5db4a2c8-24f4-409b-b437-6120682cc518 ro noautogroup transparent_hugepage=never nomdmonddf nomdmonisw

Answers:


1

nohz=off在引导过程中添加到内核​​参数以禁用它。

此选项使RCU尝试加速宽限期,以允许CPU更快地进入dynticks-idle状态。另一方面,此选项增加了dynticks-idle检查的开销,尤其是在具有大量CPU的系统上。

您似乎受到了加粗部分的影响。

更多阅读...

By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.