catapult-project / catapult

Deprecated Catapult GitHub. Please instead use http://crbug.com "Speed>Benchmarks" component for bugs and https://chromium.googlesource.com/catapult for downloading and editing source code..
https://chromium.googlesource.com/catapult
BSD 3-Clause "New" or "Revised" License
1.91k stars 562 forks source link

Unable to select a master clock domain because no path can be found from "SYSTRACE" to "LINUX_FTRACE_GLOBAL". #4612

Open alxhoff opened 5 years ago

alxhoff commented 5 years ago

I am able to open the documentation tutorial's example traces from here but when I run my own systrace I get the following error:

Import error Unable to select a master clock domain because no path can be found from "SYSTRACE" to "LINUX_FTRACE_GLOBAL".

I tried the most simplest of traces:

./systrace.py sched

which results in

Starting tracing (stop with enter) Tracing completed. Collecting output... Outputting Systrace results... Tracing complete, writing results

Wrote trace HTML file: file:///home/alxhoff/Android/Sdk/platform-tools/systrace/trace.html

But fails to open. I am getting the error in both Chromium ( 71.0.3578.98) and Chrome (71.0.3578.80), while firefox (64.0) simply displays a blank screen. This is a duplicate of #4587 but unfortunately the solution found there does not work for me.

My board (Odroid XU3) is running Android 4.4.4 and kernel 3.10.9. My system is running Arch Linux kernel 4.19.8-arch1-1-ARCH.

A sample of a trace file that is not working for me is located here.

Cheers

alxhoff commented 5 years ago

As a sanity check for my system I ran a systrace with my phone (Pixel XL) and the systrace worked. This is thus a problem with my Android 4.4.4 Odroid XU3 board. I cannot find anything in the documentation as to why this would be happening. Cheers

jsonhu commented 5 years ago

same problem, so confusing

alxhoff commented 5 years ago

I updated the board's Android version to 7.1 and it worked. So the problem lies with an incompatibility with 4.4.4 or maybe the kernel config I was using then.