From: Dave Jones <davej@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: __ftrace_hash_rec_update FTRACE_WARN_ON.
Date: Fri, 5 Jul 2013 10:26:29 -0400 [thread overview]
Message-ID: <20130705142629.GA325@redhat.com> (raw)
WARNING: at kernel/trace/ftrace.c:1605 __ftrace_hash_rec_update.part.37+0x20a/0x240()
Modules linked in: sctp libcrc32c snd_seq_dummy fuse tun rfcomm bnep scsi_transport_iscsi hidp nfnetlink can_bcm irda caif_socket nfc caif netrom crc_ccitt rose x25 appletalk ipt_ULOG rds bluetooth can_raw ipx phonet can rfkill af_802154 pppoe pppox p8023 llc2 af_key ppp_generic psnap p8022 atm llc slhc ax25 af_rxrpc snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_seq pcspkr snd_seq_device snd_pcm e1000e snd_page_alloc snd_timer snd ptp soundcore pps_core
CPU: 1 PID: 15820 Comm: trinity-child2 Not tainted 3.10.0+ #21
ffffffff81a1f20b ffff8801be9dfc60 ffffffff816f2120 0000000000000000
ffff8801be9dfc98 ffffffff8104ca81 0000000000000000 0000000000000001
ffff8801be424000 0000000000000000 ffff88022bd25518 ffff8801be9dfca8
Call Trace:
[<ffffffff816f2120>] dump_stack+0x4e/0x82
[<ffffffff8104ca81>] warn_slowpath_common+0x61/0x80
[<ffffffff8104cb5a>] warn_slowpath_null+0x1a/0x20
[<ffffffff8111489a>] __ftrace_hash_rec_update.part.37+0x20a/0x240
[<ffffffff811168a8>] ftrace_shutdown+0xb8/0x170
[<ffffffff81116d40>] unregister_ftrace_function+0x30/0x50
[<ffffffff81134487>] perf_ftrace_event_register+0x87/0x130
[<ffffffff811342ec>] perf_trace_destroy+0x2c/0x50
[<ffffffff8113caf9>] tp_perf_event_destroy+0x9/0x10
[<ffffffff8113f0f7>] free_event+0xa7/0x310
[<ffffffff8113f3c4>] perf_event_release_kernel+0x64/0x90
[<ffffffff8113f830>] put_event+0x120/0x1b0
[<ffffffff8113f740>] ? put_event+0x30/0x1b0
[<ffffffff8113f8d0>] perf_release+0x10/0x20
[<ffffffff811b7d15>] __fput+0xf5/0x2d0
[<ffffffff811b7fae>] ____fput+0xe/0x10
[<ffffffff8107798c>] task_work_run+0xac/0xe0
[<ffffffff81051d27>] do_exit+0x2c7/0xcd0
[<ffffffff81704b00>] ? ftrace_call+0x5/0x2f
[<ffffffff81053afc>] do_group_exit+0x4c/0xc0
[<ffffffff81053b84>] SyS_exit_group+0x14/0x20
[<ffffffff817050d4>] tracesys+0xdd/0xe2
---[ end trace df06ab36fcd44d8b ]---
1605 if (FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0))
1606 return;
next reply other threads:[~2013-07-05 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 14:26 Dave Jones [this message]
2013-07-05 14:53 ` __ftrace_hash_rec_update FTRACE_WARN_ON Steven Rostedt
2013-07-05 15:11 ` Dave Jones
2013-07-24 16:04 ` Jörn Engel
2013-07-25 1:24 ` Steven Rostedt
2013-07-25 5:46 ` Steve Hodgson
2013-07-25 18:59 ` Steven Rostedt
2013-07-26 3:23 ` Steven Rostedt
2013-07-27 19:16 ` Steve Hodgson
2013-07-31 0:51 ` Steven Rostedt
2013-08-02 4:51 ` Steve Hodgson
2013-08-02 11:02 ` Steven Rostedt
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=20130705142629.GA325@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.