[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEKwDSAucy8NziB=mcem7we9vnGHe=cWt-4Q1X7+Vt5dokY19A@mail.gmail.com>
Date: Thu, 17 Oct 2013 16:43:08 -0400
From: Bob Copeland <me@...copeland.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Arend van Spriel <arend@...adcom.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: trace-cmd problem with FC19
[sorry, resent for the archives, I failed email]
On Thu, Oct 17, 2013 at 4:20 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 17 Oct 2013 22:07:15 +0200
> "Arend van Spriel" <arend@...adcom.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.
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists