|
From: Robert R. <rob...@am...> - 2009-11-04 10:30:26
|
On 03.11.09 10:21:40, job...@ao... wrote: > I tried that and am still seeing the "bad magic number" error when > running opreport and "Invalid argument" entries in oprofiled.log. > > > The commands I am using and part of oprofiled.log follow. Any > suggestions? > > Eclipse # rm /var/lib/oprofile/samples/oprofiled.log > Eclipse # rm -rf /var/lib/oprofile/samples/current/ > Eclipse # cd /usr/bin/ > Eclipse # ./opcontrol --init > mount: mounting nodev on /dev/oprofile failed: Device or resource busy There is an error mounting oprofilefs, try the following steps to debug this: First, unmount /dev/oprofile if it is there. The script tries to mount the oprofile filesystem that the kernel should provide. It checks /proc/filesystems, you should get something like this on your system: # cat /proc/filesystems | grep oprofile nodev oprofilefs If it is not there, the script tries then to load the oprofile module and checks the filesystem again. oprofile should then be listed in /proc/modules and also oprofilefs in /proc/filesystems. If not, the script fails. Maybe /proc is disabled or not available? Not sure if this is a config option. You can also try to mount oprofile directly: # mkdir /dev/oprofile # mount -t oprofilefs nodev /dev/oprofile Also, it seems you are using an own build of oprofile, which version are you using. Did you use configure/make/make install to install the package on your system? Which config did you use to compile your kernel? -Robert -- Advanced Micro Devices, Inc. Operating System Research Center email: rob...@am... |