trace-cmd-start-tracing.sh fails to starts with regexp error

[LordOfDragons]

System: GenToo 64-bit

Action to reproduce:

1. Run "./trace-cmd-setup.sh", enter root password
2. Run "./trace-cmd-start-tracing.sh"

Expected result: Command succeeds

Actual result:

trace-cmd reset
trace-cmd: No such file or directory
  opening to '/sys/kernel/tracing/tracing_max_latency'

trace-cmd start -C mono -b 8000 -D -i -e sched:sched_switch -e sched:sched_process_fork -e sched:sched_process_exec -e sched:sched_process_exit -e drm:drm_vblank_event -e drm:drm_vblank_event_queued -e drm:drm_vblank_event_delivered -e amdgpu:amdgpu_vm_flush -e amdgpu:amdgpu_cs_ioctl -e amdgpu:amdgpu_sched_run_job -e *fence:*fence_signaled -e i915:i915_flip_request -e i915:i915_flip_complete -e i915:intel_gpu_freq_change -e i915:i915_gem_request_add -e i915:i915_gem_request_submit -e i915:i915_gem_request_in -e i915:i915_gem_request_out -e i915:i915_gem_request_queue -e i915:intel_engine_notify -e i915:i915_gem_request_wait_begin -e i915:i915_gem_request_wait_end -e i915:i915_request_add -e i915:i915_request_submit -e i915:i915_request_in -e i915:i915_request_out -e i915:i915_request_queue -e i915:i915_request_wait_begin -e i915:i915_request_wait_end -e i915:i915_request_retire -e i915:i915_request_execute -e i915:i915_pipe_update_vblank_evaded

trace-cmd stat

Events:
 Individual systems:
   drm
 Individual events:
    amdgpu
        amdgpu_cs_ioctl
        amdgpu_sched_run_job
        amdgpu_vm_flush
    dma_fence
        dma_fence_signaled
    sched
        sched_switch
        sched_process_exit
        sched_process_fork
        sched_process_exec

Buffer size in kilobytes (per cpu):
   8000

Buffer total size in kilobytes:
   64000

Clock: mono

Tracing is enabled

awk: cmd. line:3: warning: regexp escape sequence `\:' is not a known regexp operator
/sys/kernel/tracing/per_cpu/cpu0/stats entries:142 overrun:0 time:0.026693 sec
/sys/kernel/tracing/per_cpu/cpu1/stats entries:44 overrun:0 time:0.026986 sec
/sys/kernel/tracing/per_cpu/cpu2/stats entries:49 overrun:0 time:0.026994 sec
/sys/kernel/tracing/per_cpu/cpu3/stats entries:35 overrun:0 time:0.026403 sec
/sys/kernel/tracing/per_cpu/cpu4/stats entries:54 overrun:0 time:0.026894 sec
/sys/kernel/tracing/per_cpu/cpu5/stats entries:28 overrun:0 time:0.026428 sec
/sys/kernel/tracing/per_cpu/cpu6/stats entries:49 overrun:0 time:0.025293 sec
/sys/kernel/tracing/per_cpu/cpu7/stats entries:18 overrun:0 time:0.025415 sec

[mikesart]

I really have no idea what's going on. It looks like trace-cmd itself is spewing the "No such file or directory" error?

I don't have access to any GenToo systems. I'm happy to help you debug this, but it's mostly going to be you looking at the bash scripts and trying things. Sorry...

[LordOfDragons]

Looks like the not found file mentioned belongs to the kernel option "CONFIG_IRQSOFF_TRACER" which is by default disabled. How important is this? The kernel optionals mentions the kernel overhead is increased if used.

I noticed I can continue after this command reporting an issue with the file. I can record a trace and load it. Loading it takes ages and then hard-locks the PC in such a way not even the 5s power button reboot is working. This is bad. Could this be linked or is the application simply not compatible with my AMD system?

[pallaswept]

Saw this on opensuse tumbleweed. It's just the spaces in those regexp breaking them apart. Wrapping them in '' and handling the escaping explicitly, sorts that out. Hope that helps.