It seems that the patch in http://lists.infradead.org/pipermail/linux- arm-kernel/2011-March/045283.html is going to fix the issue by enabling pmu events for omap4, which are routed from CTI. The patch attached is a version of the above with removal of some CTI register reads that cause hang in the initial phase of booting. The patch has been verified on Panda board and the profile data could be generated that are shown by opreport. Although, there is a lockdep warning "possible circular locking dependency detected" when "opcontrol --start" is called for the first time.
** Patch added: "0001-arm-pmu-support-pmu-perf-on-OMAP4.patch" https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/702999/+attachment/2016187/+files/0001-arm-pmu-support-pmu-perf-on-OMAP4.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/702999 Title: oprofile failure on panda (omap4) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
