Oprofile 编译使用过程中遇到的几个错误

Oprofile Error: Failed to open profile device: Device or resource busy

#sudo opcontrol --start

ATTENTION: Use of opcontrol is discouraged.  Please see the man page for operf.
Using default event: CPU_CLK_UNHALTED:100000:0:1:1
Using 2.6+ OProfile kernel interface.
Reading module info.
Failed to open profile device: Device or resource busy
Couldn't start oprofiled.
Check the log file "/var/lib/oprofile/samples/oprofiled.log" and kernel syslog

牛人解释:

Before running the oprofile, you should check wether your system exists watchdog. watchdog/nmi_watchdog registers with the perf subsystem which will blocking oprofile from working. You may have to stop the watchdog/NMI watchdog to free up counter 0 using the following:

执行下面命令,解决:

echo "0" | sudo tee /proc/sys/kernel/watchdog
echo "0" | sudo tee /proc/sys/kernel/watchdog