From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: peterz@infradead.org
Subject: ye olde task_ctx_sched_out trace.
Date: Wed, 21 May 2014 11:06:13 -0400 [thread overview]
Message-ID: <20140521150613.GA28702@redhat.com> (raw)
I thought we had this nailed down a while ago, but it still keeps
popping up...
WARNING: CPU: 3 PID: 32310 at kernel/events/core.c:2384 task_ctx_sched_out+0x6b/0x80()
CPU: 3 PID: 32310 Comm: trinity-c185 Not tainted 3.15.0-rc5+ #214
0000000000000009 000000003d7dfb5c ffff880019671df8 ffffffff9371a1fd
0000000000000000 ffff880019671e30 ffffffff9306d5dd ffff88024d0d6d48
ffff88010c4944e8 0000000000000286 ffff880243b82d00 ffff88010c4944e8
Call Trace:
[<ffffffff9371a1fd>] dump_stack+0x4e/0x7a
[<ffffffff9306d5dd>] warn_slowpath_common+0x7d/0xa0
[<ffffffff9306d70a>] warn_slowpath_null+0x1a/0x20
[<ffffffff931430bb>] task_ctx_sched_out+0x6b/0x80
[<ffffffff93146138>] perf_event_comm+0xc8/0x220
[<ffffffff930a19cd>] ? get_parent_ip+0xd/0x50
[<ffffffff931c025f>] set_task_comm+0x4f/0xc0
[<ffffffff93085b23>] SyS_prctl+0x1d3/0x480
[<ffffffff9372cf9f>] tracesys+0xdd/0xe2
There was on perf activity at all going on at the time.
I had told trinity to do -g vm which excludes all non-VM related syscalls.
What is perf_event_comm doing ? Is that storing some state in case
I later decide to run perf ?
Dave
next reply other threads:[~2014-05-21 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 15:06 Dave Jones [this message]
2014-05-21 15:16 ` ye olde task_ctx_sched_out trace Peter Zijlstra
2014-05-21 15:30 ` Peter Zijlstra
2014-05-21 15:32 ` Peter Zijlstra
2014-05-22 6:52 ` Adrian Hunter
2014-05-22 7:04 ` Peter Zijlstra
2014-05-22 7:10 ` Adrian Hunter
2014-05-22 7:20 ` Peter Zijlstra
2014-05-22 7:22 ` Peter Zijlstra
2014-05-28 8:02 ` Adrian Hunter
2014-06-06 12:19 ` [tip:perf/core] perf: Differentiate exec() and non-exec() comm events tip-bot for Adrian Hunter
2014-06-06 12:19 ` [tip:perf/core] perf: Fix perf_event_comm() vs. exec() assumption tip-bot for Peter Zijlstra
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=20140521150613.GA28702@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.