Messages in this thread | | | Date | Thu, 17 Oct 2013 16:56:56 -0400 | From | Steven Rostedt <> | Subject | Re: trace-cmd problem with FC19 |
| |
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
| |