Why visual profiler fails to gather all information ?

[Romant]

What can be the reason of messages below ?

NV_Warning: Signal shared_load can not be profiled in this run.
NV_Warning: Signal shared_store can not be profiled in this run.
NV_Warning: Signal branch can not be profiled in this run.
NV_Warning: Signal warps_launched can not be profiled in this run.
NV_Warning: Signal active_cycles can not be profiled in this run.
NV_Warning: Signal sm_cta_launched can not be profiled in this run.
NV_Warning: Signal l1_global_load_hit can not be profiled in this run.
NV_Warning: Profiler counters are disabled for this context.

As a result, that’s the only info that profiler provides (under the standard header of profiler output table):

1.44997e+07 Kernel 7259.71 4.932 60 640 23040 0 50 0.417 0

[buse385]

Hi Romant,
I know it’s a little bit late for a reply, but I saw your post as I was googling for the same problem. Guess, you know the answer by now, but for people who needs this info:

Up to 4 counters can be used for profiling. You can use as many options as you want but allowed to use only 4 counters at max.

I tried and yes, this is the case.

(according to: http://www.cs264.org/lectures/files/cs264_lab5.pdf – slide 55)