From: 陳政柏 <threesmaller@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] NMI Watchdog warning
Date: Wed, 29 Apr 2015 10:51:21 +0800 [thread overview]
Message-ID: <CAGw-6wYM07jGJjmk+aSvSThw3yZ9GJN7r1hLDBAWahaR3Ayt4g@mail.gmail.com> (raw)
Hi,all
When I enabled nmi_watchdog, and I get following warning messages. How
can I resolve it?
Kernel version is 3.10.52
[ 940.093592] ------------[ cut here ]------------
[ 940.098218] WARNING: at kernel/watchdog.c:245
watchdog_overflow_callback+0x94/0xc0()
[ 940.105960] Watchdog detected hard LOCKUP on cpu 3
[ 940.110583] Modules linked in: nf_conntrack_netlink udptap(O)
nf_conntrack_ipv6 xt_socket nf_defrag_ipv6 xt_mac ip6table_mangle
nf_nat_proto_udplite nf_conntrack_proto_udplite nf_nat_proto_sctp
nf_conntrack_proto_sctp nf_nat_tftp nf_conntrack_tftp nf_conntrack_h323
nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
xt_hashlimit xt_mconnlimit xt_CT xt_TCPMSS ipt_REJECT ipt_MASQUERADE
xt_REDIRECT xt_multiport ipt_ULOG xt_NFLOG nfnetlink_log ip6table_filter
xt_set(O) xt_mark xt_connmark xt_conntrack xt_ifgroup iptable_raw ip_gre
ip_tunnel gre ip_set_hash_ip(O) ip_set_hash_netiface(O) ip_set_hash_net(O)
ip_set(O) nfnetlink nf_nat_ftp nf_conntrack_ftp xt_recent iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
iptable_mangle iptable_filter coretemp bridge dummy rte_kni(O) igb_uio(O)
uio_pci_generic uio ixgbe(O) igb(O) e1000e(O)
[ 940.188695] CPU: 3 PID: 1261 Comm: XXX Tainted: G W O 3.10.52 #1
[ 940.205210] 0000000000000009 ffff88087f8c6c78 ffffffff8148ec62
ffff88087f8c6cb0
[ 940.212667] ffffffff8103c5dc ffff88085f834c00 0000000000000000
ffff88087f8c6dd8
[ 940.220126] ffff88087f8c6ef8 0000000000000000 ffff88087f8c6d10
ffffffff8103c647
[ 940.227586] Call Trace:
[ 940.230032] <NMI> [<ffffffff8148ec62>] dump_stack+0x19/0x1b
[ 940.235803] [<ffffffff8103c5dc>] warn_slowpath_common+0x5c/0x80
[ 940.241811] [<ffffffff8103c647>] warn_slowpath_fmt+0x47/0x50
[ 940.247555] [<ffffffff81090d34>] watchdog_overflow_callback+0x94/0xc0
[ 940.254088] [<ffffffff810a38fd>] __perf_event_overflow+0x8d/0x2b0
[ 940.260271] [<ffffffff810a26b9>] ? perf_event_update_userpage+0x19/0x100
[ 940.267061] [<ffffffff810a4294>] perf_event_overflow+0x14/0x20
[ 940.272988] [<ffffffff810144de>] intel_pmu_handle_irq+0x1de/0x370
[ 940.279172] [<ffffffff8100e89b>] perf_event_nmi_handler+0x2b/0x50
[ 940.285352] [<ffffffff81006098>] do_nmi+0x118/0x420
[ 940.290315] [<ffffffff81492b8a>] end_repeat_nmi+0x1e/0x2e
[ 940.295804] <<EOE>>
[ 940.297902] ---[ end trace 3ff3d9e5ad439b5f ]---
--
Sincerely yours,
threesmaller
reply other threads:[~2015-04-29 2:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGw-6wYM07jGJjmk+aSvSThw3yZ9GJN7r1hLDBAWahaR3Ayt4g@mail.gmail.com \
--to=threesmaller@gmail.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).