On 06/12/2013 07:16 PM, Steven Rostedt wrote:
On Wed, 2013-06-12 at 12:22 -0400, Steven Rostedt wrote:
# sudo trace-cmd record -e brcmfmac:brcmf_dbg -f 'level & 0x4'
disable all
enable brcmfmac:brcmf_dbg
path = /sys/kernel/debug/tracing/events/brcmfmac/brcmf_dbg/enable
(level & 0x4)
^
p
On 06/12/2013 07:16 PM, Steven Rostedt wrote:
On Wed, 2013-06-12 at 12:22 -0400, Steven Rostedt wrote:
# sudo trace-cmd record -e brcmfmac:brcmf_dbg -f 'level & 0x4'
disable all
enable brcmfmac:brcmf_dbg
path = /sys/kernel/debug/tracing/events/brcmfmac/brcmf_dbg/enable
(level & 0x4)
^
p
On Wed, 2013-06-12 at 12:22 -0400, Steven Rostedt wrote:
> > # sudo trace-cmd record -e brcmfmac:brcmf_dbg -f 'level & 0x4'
> > disable all
> > enable brcmfmac:brcmf_dbg
> > path = /sys/kernel/debug/tracing/events/brcmfmac/brcmf_dbg/enable
> > (level & 0x4)
> > ^
> > parse_error: Invalid o
On Wed, 2013-06-12 at 12:13 +0200, Arend van Spriel wrote:
> Hi Steven
>
> I wanted to filter my debug events getting only one specific level. So I
> followed the instruction found online, but I get a parse error.
>
> Running on 3.10-rc1 using trace-cmd 1.0.3. Should I upgrade?
I would recommen
Hi Steven
I wanted to filter my debug events getting only one specific level. So I
followed the instruction found online, but I get a parse error.
Running on 3.10-rc1 using trace-cmd 1.0.3. Should I upgrade?
Regards,
Arend
8<
5 matches
Mail list logo