From: Srinivas S. <sri...@gm...> - 2006-01-27 05:29:20
|
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. Thanks, _Sidharth On 1/26/06, Srinivas Sidharth <sri...@gm...> wrote: > Hi I'm trying to use oprofile in timer interrupt mode with an SMP MIPS > linux 2.6.9 kernel and I cant get opreport to give me any useful > information. Can you guys please take a look at the messages I see and > let me know what could be going wrong? > > Thanks, > _Sidharth > > I'm using the latest oprofile 0.9.1 package. > > Are there any compatibility issues with using 0.9.1 version of this > package with a kernel 2.6.9 for the MIPS platform? If so, what version > of the package should I use? I cant change to using the latest linux > kernel without a lot of patching in the kernel. > > Since I dont have root permissions on the target (NFS mounted root fs) > I had to modify the scripts (opcontrol, etc.) to work with an > alternate install area. > > To start with I want to do some really basic kernel fuction call > histogram based profiling. For this, I'm doing: > > bash-3.00# ./utils/opcontrol --vmlinux=3D./vmlinux > using oprofile dir /home/guest/oprofile-0.9.1 > > bash-3.00# ./utils/opcontrol --start-daemon > using oprofile dir /home/guest/sri/oprofile-0.9.1 > Using 2.6+ OProfile kernel interface. > Reading module info. > Daemon started. > bash-3.00# Failed to open device. Possibly you have passed incorrect > parameters. Check /var/log/messages. > > bash-3.00# ./utils/opcontrol --start -V > using oprofile dir /home/guest/oprofile-0.9.1 > Parameters used: > CPUTYPE timer > BUF_SIZE default value > CPU_BUF_SIZE default value > SEPARATE_LIB 0 > SEPARATE_KERNEL 0 > SEPARATE_THREAD 0 > SEPARATE_CPU 0 > CALLGRAPH 0 > VMLINUX ./vmlinux > KERNEL_RANGE 80100000,803e3f38 > executing oprofiled --separate-lib=3D0 --separate-kernel=3D0 > --separate-thread=3D0 --separate-cpu=3D0 --events=3D --vmlinux=3D./vmlinu= x.sri > --kernel-range=3D80100000,803e3f38 --verbose=3Dall > Using 2.6+ OProfile kernel interface. > kernel_start =3D 80100000, kernel_end =3D 803e3f38 > Reading module info. > Daemon started. > Profiler running. > Failed to open device. Possibly you have passed incorrect > parameters. Check /var/log/messages.bash-3.00# > > bash-3.00# ./utils/opcontrol --status > using oprofile dir /home/guest/oprofile-0.9.1 > Daemon not running > Separate options: none > vmlinux file: ./vmlinux > Image filter: none > Call-graph depth: 0 > > bash-3.00# ls -l /dev/oprofile/stats/cpu4 > total 0 > -r--r--r-- 1 root root 0 Dec 31 16:01 backtrace_aborted > -r--r--r-- 1 root root 0 Dec 31 16:01 sample_lost_overflow > -r--r--r-- 1 root root 0 Dec 31 16:01 sample_received > bash-3.00# ls -l /dev/oprofile/stats/cpu0 > total 0 > -r--r--r-- 1 root root 0 Dec 31 16:01 backtrace_aborted > -r--r--r-- 1 root root 0 Dec 31 16:01 sample_lost_overflow > -r--r--r-- 1 root root 0 Dec 31 16:01 sample_received > |
From: John L. <le...@mo...> - 2006-01-27 09:12:21
|
On Thu, Jan 26, 2006 at 10:29:17PM -0700, Srinivas Sidharth wrote: > I'm getting the following output. The estimated CPU speed seems like a > problem. Any idea what could be wrong? We need the core file. john |
From: SeveQ <Se...@sy...> - 2006-02-23 09:36:16
|
Hello, there it is - the corefile of a opreport segfault: http://www.syncro-community.de/opreport_core I hope that helps... ('cos I've run into the same problems) kind regards, Hendrik Wiese -- View this message in context: http://www.nabble.com/opreport-Segmentation-Fault-%28MIPS-SMP-%29-t1008355.html#a3085060 Sent from the oprofile-list forum at Nabble.com. |
From: Philippe E. <ph...@wa...> - 2006-01-27 10:47:48
|
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 |
From: Srinivas S. <sri...@gm...> - 2006-01-27 19:10:05
|
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 <ph...@wa...> 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 > > |
From: Philippe E. <ph...@wa...> - 2006-01-27 19:29:04
|
On Fri, 27 Jan 2006 at 11:09 +0000, Srinivas Sidharth wrote: > OK. I'll try it. > > What about the CPU speed estimate as 0MHz. Where do you think the problem > could be? > A missing piece of code in libutil/op_cpufreq.c or this information is not present in /proc/cpuinfo. regards, Philippe Elie |
From: Srinivas D. <the...@gm...> - 2006-01-27 19:41:35
|
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, Philippe Elie <ph...@wa...> wrote: > > On Fri, 27 Jan 2006 at 11:09 +0000, Srinivas Sidharth wrote: > > > OK. I'll try it. > > > > What about the CPU speed estimate as 0MHz. Where do you think the > problem > > could be? > > > > A missing piece of code in libutil/op_cpufreq.c or this information > is not present in /proc/cpuinfo. > > regards, > Philippe Elie > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list > |
From: Srinivas S. <sri...@gm...> - 2006-01-27 19:44:10
|
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 <sri...@gm...> 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 <ph...@wa...> 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 > > > > > |
From: Philip M. <mu...@cs...> - 2006-01-30 19:36:11
|
Hi all, I haven't exactly looked at the code, but I can tell you that MIPS/Linux does not provide a CPU/Mhz field in /proc/cpuinfo nor is there any sort of /dev/cpuid to access the identifiers available through the MFC0 instruction. A workaround is to use the BogoMIPS field which, at least on my 20/25K Malta boards is the megahertz. Phil On Fri, 2006-01-27 at 11:43 -0800, Srinivas Sidharth wrote: > 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 <sri...@gm...> 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 <ph...@wa... > 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 > > > > |