Re: trace-cmd problem with FC19
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 installed in ~/bin. Sorry for the noise. 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 distro version may be fine, for all I know. Indeed saw your post googling for this error message, which is why I cloned trace-cmd repo. Going to sit in a corner feeling stupid :-( Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 installed in ~/bin. Sorry for the noise. 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 distro version may be fine, for all I know. Indeed saw your post googling for this error message, which is why I cloned trace-cmd repo. Going to sit in a corner feeling stupid :-( Regards, Arend -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 referenced issue using an older, > self-compiled version with a recent kernel. The FC19 distro > version may be fine, for all I know. > > Arend says he used the latest version from the repo which should > not be a problem, but just throwing that out there since the > symptoms are similar. > Yeah, there was a known breakage in 3.10. The problem was that the breakage was a fix to the splice code that would help trace-cmd. Unfortunately, trace-cmd had a bug in it that would cause the fix to break it. I released a fix for all versions of trace-cmd that's currently supported, and some that are not (all the way down to the 1.0 series). I had the fix go out several months before 3.10 was released, and notified all the major distros about it. Thus, if you are using an older version, then yes, it will be broken with the newer kernel. Just upgrade to a newer release (you can even keep the same X.X version as they all have the fix). -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 distro version may be fine, for all I know. Arend says he used the latest version from the repo which should not be a problem, but just throwing that out there since the symptoms are similar. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 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-6pVB5Lsystemd-private-KdpFqS trace.dat.cpu0 > >> trace.dat.cpu2 > >> systemd-private-9hedRDtrace.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 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 trace-cmd record -e ext4:* ls >> /sys/kernel/debug/tracing/events/ext4/*/filter >> systemd-private-6pVB5Lsystemd-private-KdpFqS trace.dat.cpu0 >> trace.dat.cpu2 >> systemd-private-9hedRDtrace.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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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-6pVB5Lsystemd-private-KdpFqS trace.dat.cpu0 > trace.dat.cpu2 > systemd-private-9hedRDtrace.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 > trace-cmd: Interrupted system call >recorder error in splice input > Kernel buffer statistics: >Note: "entries" are the entries left in the kernel ring buffer and > are not > recorded in the trace data. They should all be zero. > > I got the modules properly signed so only OOT taint is set and it still > does not work. You said this is an issue on Fedora 19? I have a Fedora 19 VM, and did the following: $ su # yum install trace-cmd # trace-cmd record -e ext4:* ls and it all worked. Now the difference is that I don't use sudo (I find it rather silly). Do you get the same error with 'su' as you do with 'sudo'? -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 ok, but adding it. I use it almost daily on Ubuntu system, but trying Fedora for a change. I do have a difference with kernel taint with my driver loaded: Ubuntu 4096(OOT module loaded, ie. my driver) Fedora 4098(OOT *and* forced module?) 'forced module' probably caused by: [10808.074823] Request for unknown module key 'Fedora kernel signing key: 8661dbf3061bfa70eb76d61691cec200318534b4' err -11 Would that explain my issue? Regards, Arend ---8< $ sudo trace-cmd record -e brcmfmac:* /sys/kernel/debug/tracing/events/brcmfmac/*/filter Hit Ctrl^C to stop recording ^Ctrace-cmd: Interrupted system call trace-cmd: Interrupted system call recorder error in splice inputrecorder error in splice input I haven't seen this before. Was the brcmfmac module the one that was forced loaded? 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 trace-cmd: Interrupted system call recorder error in splice input Kernel buffer statistics: Note: "entries" are the entries left in the kernel ring buffer and are not recorded in the trace data. They should all be zero. I got the modules properly signed so only OOT taint is set and it still does not work. Regards, Arend -- Steve trace-cmd: Interrupted system call recorder error in splice input trace-cmd: Interrupted system call recorder error in splice input Kernel buffer statistics: Note: "entries" are the entries left in the kernel ring buffer and are not recorded in the trace data. They should all be zero. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 it almost daily on Ubuntu system, but trying Fedora for a change. > I do have a difference with kernel taint with my driver loaded: > > Ubuntu4096(OOT module loaded, ie. my driver) > Fedora4098(OOT *and* forced module?) > > 'forced module' probably caused by: > [10808.074823] Request for unknown module key 'Fedora kernel signing > key: 8661dbf3061bfa70eb76d61691cec200318534b4' err -11 > > Would that explain my issue? > > Regards, > Arend > > ---8< > $ sudo trace-cmd record -e brcmfmac:* > /sys/kernel/debug/tracing/events/brcmfmac/*/filter > Hit Ctrl^C to stop recording > ^Ctrace-cmd: Interrupted system call > trace-cmd: Interrupted system call > recorder error in splice inputrecorder error in splice input I haven't seen this before. Was the brcmfmac module the one that was forced loaded? Does recording other traces work? Or is it only spicific to this module? -- Steve > > trace-cmd: Interrupted system call >recorder error in splice input > trace-cmd: Interrupted system call >recorder error in splice input > Kernel buffer statistics: >Note: "entries" are the entries left in the kernel ring buffer and > are not > recorded in the trace data. They should all be zero. > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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. I use it almost daily on Ubuntu system, but trying Fedora for a change. I do have a difference with kernel taint with my driver loaded: Ubuntu4096(OOT module loaded, ie. my driver) Fedora4098(OOT *and* forced module?) 'forced module' probably caused by: [10808.074823] Request for unknown module key 'Fedora kernel signing key: 8661dbf3061bfa70eb76d61691cec200318534b4' err -11 Would that explain my issue? Regards, Arend ---8 $ sudo trace-cmd record -e brcmfmac:* /sys/kernel/debug/tracing/events/brcmfmac/*/filter Hit Ctrl^C to stop recording ^Ctrace-cmd: Interrupted system call trace-cmd: Interrupted system call recorder error in splice inputrecorder error in splice input I haven't seen this before. Was the brcmfmac module the one that was forced loaded? Does recording other traces work? Or is it only spicific to this module? -- Steve trace-cmd: Interrupted system call recorder error in splice input trace-cmd: Interrupted system call recorder error in splice input Kernel buffer statistics: Note: entries are the entries left in the kernel ring buffer and are not recorded in the trace data. They should all be zero. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 configuration looks ok, but adding it. I use it almost daily on Ubuntu system, but trying Fedora for a change. I do have a difference with kernel taint with my driver loaded: Ubuntu 4096(OOT module loaded, ie. my driver) Fedora 4098(OOT *and* forced module?) 'forced module' probably caused by: [10808.074823] Request for unknown module key 'Fedora kernel signing key: 8661dbf3061bfa70eb76d61691cec200318534b4' err -11 Would that explain my issue? Regards, Arend ---8 $ sudo trace-cmd record -e brcmfmac:* /sys/kernel/debug/tracing/events/brcmfmac/*/filter Hit Ctrl^C to stop recording ^Ctrace-cmd: Interrupted system call trace-cmd: Interrupted system call recorder error in splice inputrecorder error in splice input I haven't seen this before. Was the brcmfmac module the one that was forced loaded? 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 trace-cmd: Interrupted system call recorder error in splice input Kernel buffer statistics: Note: entries are the entries left in the kernel ring buffer and are not recorded in the trace data. They should all be zero. I got the modules properly signed so only OOT taint is set and it still does not work. Regards, Arend -- Steve trace-cmd: Interrupted system call recorder error in splice input trace-cmd: Interrupted system call recorder error in splice input Kernel buffer statistics: Note: entries are the entries left in the kernel ring buffer and are not recorded in the trace data. They should all be zero. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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-6pVB5Lsystemd-private-KdpFqS trace.dat.cpu0 trace.dat.cpu2 systemd-private-9hedRDtrace.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 trace-cmd: Interrupted system call recorder error in splice input Kernel buffer statistics: Note: entries are the entries left in the kernel ring buffer and are not recorded in the trace data. They should all be zero. I got the modules properly signed so only OOT taint is set and it still does not work. You said this is an issue on Fedora 19? I have a Fedora 19 VM, and did the following: $ su # yum install trace-cmd # trace-cmd record -e ext4:* ls and it all worked. Now the difference is that I don't use sudo (I find it rather silly). Do you get the same error with 'su' as you do with 'sudo'? -- Steve -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 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 generic issue: $ sudo trace-cmd record -e ext4:* ls /sys/kernel/debug/tracing/events/ext4/*/filter systemd-private-6pVB5Lsystemd-private-KdpFqS trace.dat.cpu0 trace.dat.cpu2 systemd-private-9hedRDtrace.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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 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-6pVB5Lsystemd-private-KdpFqS trace.dat.cpu0 trace.dat.cpu2 systemd-private-9hedRDtrace.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 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 distro version may be fine, for all I know. Arend says he used the latest version from the repo which should not be a problem, but just throwing that out there since the symptoms are similar. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: trace-cmd problem with FC19
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 referenced issue using an older, self-compiled version with a recent kernel. The FC19 distro version may be fine, for all I know. Arend says he used the latest version from the repo which should not be a problem, but just throwing that out there since the symptoms are similar. Yeah, there was a known breakage in 3.10. The problem was that the breakage was a fix to the splice code that would help trace-cmd. Unfortunately, trace-cmd had a bug in it that would cause the fix to break it. I released a fix for all versions of trace-cmd that's currently supported, and some that are not (all the way down to the 1.0 series). I had the fix go out several months before 3.10 was released, and notified all the major distros about it. Thus, if you are using an older version, then yes, it will be broken with the newer kernel. Just upgrade to a newer release (you can even keep the same X.X version as they all have the fix). -- Steve -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
