At 2013-04-30 01:10:31,"Robert Richter" <firstname.lastname@example.org> wrote:
>On 26.04.13 07:15:35, Maynard Johnson wrote:
>> Would you have any idea why this oprofile user cannot get around the
>> error below ("Error: counter 0 not available nmi_watchdog using this
>> resource ?")?
>This happens if perf is running. This either can be the perf watchdog
>(can be disabled with echo 0 > /proc/sys/kernel/nmi_watchdog) or
>another perf session (e.g. perf top etc.).
Before this server has not been installed perf. So I think perf is not running(command not found). Just now, I install it using apt-get.
>If the watchdog is disabled but another perf session is running, the
>contents of the counter registers might give you a hint what is
> # taskset $CPU echo p > /proc/sysrq-trigger
> # dmesg | tail -n 30
In my server, $CPU is NULL. How to set it?
root@nimbnode7:~# taskset $CPU echo p > /proc/sysrq-trigger
taskset: failed to parse CPU mask: echo
root@nimbnode7:~# echo $CPU
>The bit 0-7 of the PMC's ctrl register contains the event type to be