I’m having problems trying to generate analysis metrics for my other centos machine to display in the visual profiler. I can run and compile my kernel fine on the jetson board, but when using --analysis metrics, it claims “processing 0 of 32” with varying degrees of progress, and waits, doesn’t appear to do anything, then if I try to move my mouse, the mouse pointer moves a bit, stops and I can no longer interact with the device. After waiting 30 minutes, nothing happened, and I was forced to shut the device down. Profile files are blank when loaded into the visual profiler on centos. Additionally I tried doing the same thing on my centos machine with a 1070, which doesn’t have this behavior, and doesn’t lock me out of interacting with the system, though the terminal is unresponsive. It takes about a minute for the process to complete on my centos machine.
all I do is run nvprof --analysis-metrics -o filename.nvprof ./appname
Ok I’m in the process of trying to figure out which commands cause the entire system to stall. I created the script below. This script allowed me to do a sort of binary search on what commands (taken from --query–metrics) cause issue. There are a total of 120 commands listed here, every argument up until the 49th works, but the metric arguments
all freeze my system, and I suspect that the double versions don’t because I don’t use doubles in my program.
shared_efficiency also stalls
It looks like the driver can’t handle in code profile analysis? How am I supposed to profile my code if the tegra just crashes when I try? I’m installing with cuda-repo-l4t-8-0-local-8.0.34-1_arm64.deb btw.
snb4y4,
Thanks for your posting. We aren’t aware of the issue you reported but doesn’t mean there won’t be such issue. Is it possible to trim down you code to bare minimum but able to repro the issue you observed so we can try it here? Thanks again!