PGI User Forum

[RichardVerm29401]

When I try to run pgcollect using a shell script as an argument I get an error as shown below.

pgcollect -exe ../../Linux_2.6_64/bin/migkdep3 temp.sh
pgcollect-Fatal-/usr/local/pgi/linux86-64/12.9/bin/pgsampt TERMINATED by signal 11
Arguments to /usr/local/pgi/linux86-64/12.9/bin/pgsampt
/usr/local/pgi/linux86-64/12.9/bin/pgsampt temp.sh

However if I run

pgcollect ../../Linux_2.6_64/bin/migkdep3 arguments

It works. What am I missing as I have a number of test cases to run.

I am running Open Suse 11.4 64 bit version 12.9 of pgcollect.

[donb]

Sorry, this is a confusing and inconsistent part of how pgcollect works.

The use of a script as the argument, along with the use of the '-exe' option, is only intended for use with OProfile-style (aka event-based) sampling.

For basic time-based sampling, you would use the approach that worked for you below. The default sampling option, -time, will not work with a script. In this case the pgcollect command would just go in the script, preceding the invocation of the program.

Alternatively, if you have OProfile installed on the system, you could use pgcollect as you were attempting to, only with the '-hwtime' option:

[RichardVerm29401]

Thank you.

I have tried your suggestion but it seems pgcollect cannot start opcontrol

pgcollect -v -hwtime -exe ../../Linux_2.6_64/bin/migkpre profile.sh

/usr/local/pgi/linux86-64/12.9/bin/pgoprun -from-pgprof -exe ../../Linux_2.6_64/bin/migkpre -time 10 profile.sh
ATTENTION: Use of opcontrol is discouraged. Please see the man page for operf.
Error: counter 0 not available

...

Unable to complete dump of oprofile data: is the oprofile daemon running?
Daemon not running
Using /var/lib/oprofile/samples/ for samples directory.
opreport error: No sample file found: If using opcontrol for profiling,
try running 'opcontrol --dump'; otherwise, specify a session containing
sample files.

opcontrol -v
opcontrol: oprofile 0.9.8 compiled on Nov 14 2012 17:36:49

Any other suggestions?

[donb]

This error is the result of using the latest version of OProfile 0.98, which introduces 'operf', and also probably the management of the PMU (performance monitoring unit) by newer versions of Linux. There is a workaround, and we are working on a more palatable solution.

The workaround is:
- make sure that no 'perf' commands are running
- check to see that the file /proc/sys/kernel/nmi_watchdog exists
- if it does not, we will need to research your problem further
- if it does, then disable the NMI watchdog timer by running, as root:

[RichardVerm29401]

Thanks, but I just checked and I do not have an nmi_watchdog in that directory. I found

/proc/sys/kernel/panic_on_io_nmi
/proc/sys/kernel/panic_on_unrecovered_nmi

and a

watchdog
watchdog_thresh

So any other suggestions would be appreciated.