From: Dave Jones <davej@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0))
Date: Wed, 2 Oct 2013 10:16:50 -0400 [thread overview]
Message-ID: <20131002141650.GA11305@redhat.com> (raw)
In-Reply-To: <1380630531.16752.9.camel@pippen.local.home>
On Tue, Oct 01, 2013 at 08:28:51AM -0400, Steven Rostedt wrote:
> On Tue, 2013-10-01 at 00:20 -0400, Dave Jones wrote:
>
> > It seems like trace-cmd needs to be run as root. all hell will break loose if trinity gets root privs.
>
> Then run this:
>
> trace-cmd record -e syscalls -B trinity su davej -c 'trinity <args>'
I feel like I'm peeling an onion.
I keep hititng that other ftrace bug instead:
WARNING: CPU: 2 PID: 15596 at kernel/trace/ftrace.c:1701 ftrace_bug+0x206/0x270()
Modules linked in: snd_seq_dummy(+) rfcomm hidp bnep nfnetlink scsi_transport_iscsi nfc caif_socket caif af_802154 phonet af_rxrpc can_raw can_bcm bluetooth rfkill can llc2 pppoe ppp
ox ppp_generic slhc irda crc_ccitt rds ipt_ULOG af_key rose x25 atm netrom appletalk ipx p8023 psnap p8022 llc ax25 coretemp hwmon x86_pkg_temp_thermal kvm_intel xfs kvm libcrc32c snd_hda_codec_hdm
i snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq crct10dif_pclmul snd_seq_device crc32c_intel ghash_clmulni_intel snd_pcm e1000e microcode serio_raw pcspkr snd_page_alloc shpch
p usb_debug snd_timer ptp snd pps_core soundcore
CPU: 2 PID: 15596 Comm: modprobe Not tainted 3.12.0-rc3+ #92
ffffffff81a2a214 ffff880236abfc30 ffffffff8172a363 0000000000000000
ffff880236abfc68 ffffffff8105523d 0000000000000000 ffffffffa034a000
ffff880239d5b0e0 0000000000000000 ffff880234edb000 ffff880236abfc78
Call Trace:
[<ffffffff8172a363>] dump_stack+0x4e/0x82
[<ffffffff8105523d>] warn_slowpath_common+0x7d/0xa0
[<ffffffffa034a000>] ? 0xffffffffa0349fff
[<ffffffff8105531a>] warn_slowpath_null+0x1a/0x20
[<ffffffff81120776>] ftrace_bug+0x206/0x270
[<ffffffffa034a000>] ? 0xffffffffa0349fff
[<ffffffff81120aec>] ftrace_process_locs+0x30c/0x640
[<ffffffff81120e5e>] ftrace_module_notify_enter+0x3e/0x50
[<ffffffff81738aa6>] notifier_call_chain+0x66/0x150
[<ffffffff8108b197>] __blocking_notifier_call_chain+0x67/0xc0
[<ffffffff8108b206>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff810daddd>] load_module+0x1f7d/0x26a0
[<ffffffff810d5f90>] ? store_uevent+0x40/0x40
[<ffffffff810db696>] SyS_finit_module+0x86/0xb0
[<ffffffff8173d4e4>] tracesys+0xdd/0xe2
---[ end trace d2b5caf2401c5667 ]---
ftrace faulted on writing [<ffffffffa034a000>] dummy_free+0x0/0x10 [snd_seq_dummy]
This locks up hard, and then I end up with 0 byte log files when I reboot :-/
Dave
next prev parent reply other threads:[~2013-10-02 14:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 3:46 FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0)) Dave Jones
2013-08-28 13:54 ` Steven Rostedt
2013-08-28 13:58 ` Steven Rostedt
2013-08-28 15:17 ` Steven Rostedt
2013-08-28 18:27 ` Dave Jones
2013-08-28 18:29 ` Dave Jones
2013-08-28 19:27 ` Steven Rostedt
2013-09-30 17:12 ` Dave Jones
2013-10-01 3:56 ` Steven Rostedt
2013-10-01 4:20 ` Dave Jones
2013-10-01 12:28 ` Steven Rostedt
2013-10-02 14:16 ` Dave Jones [this message]
2013-10-02 16:43 ` Steven Rostedt
2013-10-02 16:53 ` Dave Jones
2013-08-28 14:31 ` Steven Rostedt
2013-08-28 16:23 ` Dave Jones
2013-08-28 16:50 ` Vince Weaver
2013-08-28 16:57 ` Steven Rostedt
2013-08-28 17:33 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2014-01-30 4:16 Dave Jones
2014-01-30 4:50 ` Steven Rostedt
2014-01-30 5:32 ` Dave Jones
2014-01-30 13:55 ` 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=20131002141650.GA11305@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox