Re: /usr/bin/opcontrol: line 1016: echo: write error: Invalid argument

[Robert R. <rob...@am...>]

On 16.10.09 22:13:34, nupur garg wrote:
> Hello,
> The output of  /bin/sh -x /usr/bin/opcontrol --start is as follows:

opcontrol fails two times:

First writing the backtrace_depth paramenter:

> + do_param_setup
>
> + test 0 '!=' 0
>
> + test 0 '!=' 0
>
> + test 0 '!=' 0
>
> + test -n ''
>
> + test 0 '!=' 0
>
> + test yes = yes -a -f /dev/oprofile/backtrace_depth
>
> + set_param backtrace_depth 0
>
> + test yes = yes
>
> + echo 0
>
> /usr/bin/opcontrol: line 1016: echo: write error: Invalid argument

and then during starting the daemon:

> + /usr/bin/oprofiled --session-dir=/var/lib/oprofile --separate-lib=0
> --separate-kernel=0 --separate-thread=0 --separate-cpu=0
> --events=CPU_CLK_UNHALTED:121:0:100000:0:1:1, --vmlinux=vmlinux
> --kernel-range=ffffffff80200000,ffffffff80266330
>
> Failed to open profile device: Operation not permitted

Writing to /dev/oprofile/backtrace_depth calls a kernel function that
returns EINVAL, you will have to look at the source of your kernel for
this.

The second fails when opening /dev/oprofile/buffer. This may only
happen if you are not root (in the upstream kernel), maybe this is
different in a xen kernel.

So, you have to look at the sources of your xen kernel, esp. the
implemented file operations in oprofile_files.c.

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: rob...@am...