Ok, I have tried this following the above steps on the 20110216/natty-preinstalled-netbook-armel images for omap (beaglexm) and omap4 (panda) with the latest updates. On the beaglexm it produces a report, however on the panda it does not.
The panda image currently uses 2.6.35-1101-omap4 kernel.
Other experiments I tried:
panda with nosmp kernel parameter (disables 2nd cpu): same results
panda with 2.6.38-1202 from kernel-team ppa: same results
The expected results look something like this (see http://paste.ubuntu.com/570812/ for the complete output from beagle XM):
CPU: ARM Cortex-A8, speed 0 MHz (estimated)
Counted CPU_CYCLES events (Number of CPU cycles) with a unit mask of 0x00 (No unit mask) count 100000
CPU_CYCLES:100000|
samples| %|
------------------
193159 70.4929 no-vmlinux
22737 8.2978 libxapian.so.22.2.0
20779 7.5832 libc-2.13.so
.
.
.
What panda produces is only this:
error: no sample files found: profile specification too strict ?
I am currently waiting on the 2.6.38-1204 kernel to finish building and will test it, but my expectations are low.
Ok, I have tried this following the above steps on the 20110216/ natty-preinstal led-netbook- armel images for omap (beaglexm) and omap4 (panda) with the latest updates. On the beaglexm it produces a report, however on the panda it does not.
The panda image currently uses 2.6.35-1101-omap4 kernel.
Other experiments I tried:
panda with nosmp kernel parameter (disables 2nd cpu): same results
panda with 2.6.38-1202 from kernel-team ppa: same results
The expected results look something like this (see http:// paste.ubuntu. com/570812/ for the complete output from beagle XM):
CPU: ARM Cortex-A8, speed 0 MHz (estimated)
Counted CPU_CYCLES events (Number of CPU cycles) with a unit mask of 0x00 (No unit mask) count 100000
CPU_CYCLES:100000|
samples| %|
------------------
193159 70.4929 no-vmlinux
22737 8.2978 libxapian.so.22.2.0
20779 7.5832 libc-2.13.so
.
.
.
What panda produces is only this:
error: no sample files found: profile specification too strict ?
I am currently waiting on the 2.6.38-1204 kernel to finish building and will test it, but my expectations are low.