Oprofile error: could not open device profile: device or resource is busy

Question

I try to run oprofile on my system due to an annoying error:

$ sudo opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux
$ 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

Anyone familiar with Oprofile will notice that I am using the correct sequence of commands to invoke the service. This comes directly from the Fedora documentation . Kernel debugging information was also installed to create the corresponding vmlinux file. But even after passing the location of this file to oprofile, there was nothing:

$ sudo opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/3.12.11-201.fc19.x86_64/vmlinux
$ 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

What else does not exist is the log file in the specified location. I tried several other solutions, including reinstalling, removing the daemon, and starting without profiling the kernel.

• Why is the device busy when there are no oprofile processes?
• Why is there no log file?
• , oprofile?

Answer 1

oprofile , . watchdog/nmi_watchdog , oprofile. , watchdog/NMI, 0, :

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

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