Re: trace-cmd problem with FC19

2013-10-18 Thread Arend van Spriel
On 10/17/2013 11:11 PM, Bob Copeland wrote: On Thu, Oct 17, 2013 at 04:56:56PM -0400, Steven Rostedt wrote: Hmm, are you sure? You may want to do both: sudo trace-cmd -v which trace-cmd Aaargh, bullocks! My home dir is an NFS mount on FC19 x64 machine and it has a 32-bit trace-cmd

Re: trace-cmd problem with FC19

2013-10-18 Thread Arend van Spriel
On 10/17/2013 11:11 PM, Bob Copeland wrote: On Thu, Oct 17, 2013 at 04:56:56PM -0400, Steven Rostedt wrote: Hmm, are you sure? You may want to do both: sudo trace-cmd -v which trace-cmd Aaargh, bullocks! My home dir is an NFS mount on FC19 x64 machine and it has a 32-bit trace-cmd

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 17:11:43 -0400 Bob Copeland wrote: > On Thu, Oct 17, 2013 at 04:56:56PM -0400, Steven Rostedt wrote: > > Hmm, are you sure? > > > > You may want to do both: > > > > sudo trace-cmd -v > > which trace-cmd > > > > to see which version it is. > > To clarify - I ran into the

Re: trace-cmd problem with FC19

2013-10-17 Thread Bob Copeland
On Thu, Oct 17, 2013 at 04:56:56PM -0400, Steven Rostedt wrote: > Hmm, are you sure? > > You may want to do both: > > sudo trace-cmd -v > which trace-cmd > > to see which version it is. To clarify - I ran into the referenced issue using an older, self-compiled version with a recent kernel.

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 16:43:08 -0400 Bob Copeland wrote: > [sorry, resent for the archives, I failed email] > On Thu, Oct 17, 2013 at 4:20 PM, Steven Rostedt wrote: > > On Thu, 17 Oct 2013 22:07:15 +0200 > > "Arend van Spriel" wrote: > > > > > >> > Does recording other traces work? Or is it only

Re: trace-cmd problem with FC19

2013-10-17 Thread Bob Copeland
[sorry, resent for the archives, I failed email] On Thu, Oct 17, 2013 at 4:20 PM, Steven Rostedt wrote: > On Thu, 17 Oct 2013 22:07:15 +0200 > "Arend van Spriel" wrote: > > >> > Does recording other traces work? Or is it only spicific to this module? >> >> It seems a generic issue: >> >> $ sudo

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 22:07:15 +0200 "Arend van Spriel" 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

Re: trace-cmd problem with FC19

2013-10-17 Thread Arend van Spriel
On 10/17/13 20:41, Steven Rostedt wrote: On Thu, 17 Oct 2013 14:08:08 +0200 "Arend van Spriel" wrote: Hi Steven, When tracing I get these error messages and no trace data is recorded. I also cloned the trace-cmd repo and tried that with the same result. I think the kernel configuration looks

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 14:08:08 +0200 "Arend van Spriel" wrote: > Hi Steven, > > When tracing I get these error messages and no trace data is recorded. I > also cloned the trace-cmd repo and tried that with the same result. I > think the kernel configuration looks ok, but adding it. > > I use

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 14:08:08 +0200 Arend van Spriel ar...@broadcom.com wrote: Hi Steven, When tracing I get these error messages and no trace data is recorded. I also cloned the trace-cmd repo and tried that with the same result. I think the kernel configuration looks ok, but adding it.

Re: trace-cmd problem with FC19

2013-10-17 Thread Arend van Spriel
On 10/17/13 20:41, Steven Rostedt wrote: On Thu, 17 Oct 2013 14:08:08 +0200 Arend van Sprielar...@broadcom.com wrote: Hi Steven, When tracing I get these error messages and no trace data is recorded. I also cloned the trace-cmd repo and tried that with the same result. I think the kernel

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 22:07:15 +0200 Arend van Spriel ar...@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

Re: trace-cmd problem with FC19

2013-10-17 Thread Bob Copeland
[sorry, resent for the archives, I failed email] On Thu, Oct 17, 2013 at 4:20 PM, Steven Rostedt rost...@goodmis.org wrote: On Thu, 17 Oct 2013 22:07:15 +0200 Arend van Spriel ar...@broadcom.com wrote: Does recording other traces work? Or is it only spicific to this module? It seems a

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 16:43:08 -0400 Bob Copeland m...@bobcopeland.com wrote: [sorry, resent for the archives, I failed email] On Thu, Oct 17, 2013 at 4:20 PM, Steven Rostedt rost...@goodmis.org wrote: On Thu, 17 Oct 2013 22:07:15 +0200 Arend van Spriel ar...@broadcom.com wrote: Does

Re: trace-cmd problem with FC19

2013-10-17 Thread Bob Copeland
On Thu, Oct 17, 2013 at 04:56:56PM -0400, Steven Rostedt wrote: Hmm, are you sure? You may want to do both: sudo trace-cmd -v which trace-cmd to see which version it is. To clarify - I ran into the referenced issue using an older, self-compiled version with a recent kernel. The FC19

Re: trace-cmd problem with FC19

2013-10-17 Thread Steven Rostedt
On Thu, 17 Oct 2013 17:11:43 -0400 Bob Copeland m...@bobcopeland.com wrote: On Thu, Oct 17, 2013 at 04:56:56PM -0400, Steven Rostedt wrote: Hmm, are you sure? You may want to do both: sudo trace-cmd -v which trace-cmd to see which version it is. To clarify - I ran into the