Thanks. I'll check it out.
 
Is there any compatibilty issue between oprofile 0.9-1 package and the oprofile driver in linux 2.6.9 kernel?
 
_Sri


On 1/27/06, Srinivas Sidharth <srinivas.sidharth@gmail.com> wrote:
OK. I'll try it.
 
What about the CPU speed estimate as 0MHz. Where do you think the problem could be?

_Sidharth

 
On 1/27/06, Philippe Elie <phil.el@wanadoo.fr > wrote:
On Thu, 26 Jan 2006 at 22:29 +0000, Srinivas Sidharth wrote:

> I'm getting the following output. The estimated CPU speed seems like a
> problem. Any idea what could be wrong?
>
>
> bash-3.00# ./pp/opreport --long-filenames
> CPU: CPU with timer interrupt, speed 0 MHz (estimated)
> Profiling through timer interrupt
>           TIMER:0|
>   samples|      %|
> ------------------
>      7871 100.000 /home/guest/oprofile-0.9.1/vmlinux
>
> bash-3.00# ./pp/opreport -g --symbols
> CPU: CPU with timer interrupt, speed 0 MHz (estimated)
> Profiling through timer interrupt
> Segmentation fault
>
> bash-3.00# ./pp/opreport --callgraph
> CPU: CPU with timer interrupt, speed 0 MHz (estimated)
> Profiling through timer interrupt
> Segmentation fault
>
> I have the 0.9.1 oprofile package with a linux 2.6.9 kernel.

I fixed a segfault occuring only when using -g, can you try the current
cvs and check if it fix your problem ?

regards,
Philippe Elie