From: Vinson Lee <vlee@twopensource.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-perf-users@vger.kernel.org
Subject: watchdog warnings on 3.4 triggered by perf
Date: Tue, 25 Mar 2014 10:56:10 -0700 [thread overview]
Message-ID: <CAHTgTXUSc6Ns-7v6JYKYR6TJCtbrKA+oka18sPTyNhaRkigncg@mail.gmail.com> (raw)
Hi.
We are seeing kernel watchdog warnings on Linux 3.4.78 on several
different machines. The warning occurs occasionally when there are
multiple instances of perf stat with an event list each tracing a
different process. This isn't a recent regression as we saw this
happen with earlier versions of 3.4.y too.
Here is the typical stack trace.
------------[ cut here ]------------
WARNING: at kernel/watchdog.c:241 watchdog_overflow_callback+0x9b/0xa6()
Watchdog detected hard LOCKUP on cpu 4
Modules linked in: netconsole configfs ipv6 dm_multipath video sbs
sbshc acpi_pad acpi_memhotplug acpi_ipmi parport_pc lp parport
tcp_diag inet_diag ipmi_si ipmi_d
andler igb dcdbas hed sb_edac i2c_i801 ioatdma i2c_core iTCO_wdt
shpchp iTCO_vendor_support edac_core wmi dca microcode
Pid: 20128, comm: java Not tainted 3.4.78 #1
Call Trace:
<NMI> [<ffffffff8103c20c>] warn_slowpath_common+0x85/0x9d
[<ffffffff8103c2c7>] warn_slowpath_fmt+0x46/0x48
[<ffffffff810689db>] ? sched_clock_cpu+0x44/0xce
[<ffffffff810ad7c4>] watchdog_overflow_callback+0x9b/0xa6
[<ffffffff810dbae7>] __perf_event_overflow+0x137/0x1c1
[<ffffffff8100fa36>] ? x86_perf_event_set_period+0x107/0x113
[<ffffffff810dbeeb>] perf_event_overflow+0x14/0x16
[<ffffffff81014406>] intel_pmu_handle_irq+0x263/0x2e0
[<ffffffff814bcc8f>] perf_event_nmi_handler+0x19/0x1b
[<ffffffff814bc663>] default_do_nmi+0x66/0x1d4
[<ffffffff814bc841>] do_nmi+0x70/0xbb
[<ffffffff814bbd0c>] end_repeat_nmi+0x1a/0x1e
<<EOE>>
---[ end trace 6a76b814d8600490 ]---
Cheers,
Vinson
reply other threads:[~2014-03-25 17:56 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=CAHTgTXUSc6Ns-7v6JYKYR6TJCtbrKA+oka18sPTyNhaRkigncg@mail.gmail.com \
--to=vlee@twopensource.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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).