From: Steven Rostedt <rostedt@goodmis.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: Arend van Spriel <arend@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: trace-cmd problem with FC19
Date: Thu, 17 Oct 2013 16:56:56 -0400 [thread overview]
Message-ID: <20131017165656.54b8b985@gandalf.local.home> (raw)
In-Reply-To: <CAEKwDSAucy8NziB=mcem7we9vnGHe=cWt-4Q1X7+Vt5dokY19A@mail.gmail.com>
On Thu, 17 Oct 2013 16:43:08 -0400
Bob Copeland <me@bobcopeland.com> wrote:
> [sorry, resent for the archives, I failed email]
> On Thu, Oct 17, 2013 at 4:20 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Thu, 17 Oct 2013 22:07:15 +0200
> > "Arend van Spriel" <arend@broadcom.com> wrote:
> >
> >
> >> > Does recording other traces work? Or is it only spicific to this module?
> >>
> >> It seems a generic issue:
> >>
> >> $ sudo trace-cmd record -e ext4:* ls
> >> /sys/kernel/debug/tracing/events/ext4/*/filter
> >> systemd-private-6pVB5L systemd-private-KdpFqS trace.dat.cpu0 trace.dat.cpu2
> >> systemd-private-9hedRD trace.dat trace.dat.cpu1 trace.dat.cpu3
> >> trace-cmd: Interrupted system call
> >> recorder error in splice input
> >> trace-cmd: Interrupted system call
> >> recorder error in splice input
> >> trace-cmd: Interrupted system call
> >> recorder error in splice input
>
> Perhaps this is an instance of this bug?
>
> https://lkml.org/lkml/2013/5/31/426
>
> tl;dr try with latest trace-cmd? I hit the above myself.
>
Hmm, are you sure?
You may want to do both:
sudo trace-cmd -v
which trace-cmd
to see which version it is.
-- Steve
next prev parent reply other threads:[~2013-10-17 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 12:08 Arend van Spriel
2013-10-17 18:41 ` Steven Rostedt
2013-10-17 20:07 ` Arend van Spriel
2013-10-17 20:20 ` Steven Rostedt
2013-10-17 20:43 ` Bob Copeland
2013-10-17 20:56 ` Steven Rostedt [this message]
2013-10-17 21:11 ` Bob Copeland
2013-10-17 23:17 ` Steven Rostedt
2013-10-18 7:21 ` Arend van Spriel
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=20131017165656.54b8b985@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.com \
/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
all inboxes | Powered by JetHome®