My system is a Core i7 920. Using Ubuntu 9.04 (jaunty). $ uname -a Linux foo 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux $ opcontrol --version opcontrol: oprofile 0.9.3 compiled on Feb 25 2009 10:54:56
Getting the same problem here too: $ sudo opcontrol --init cpu_type 'unset' is not valid you should upgrade oprofile or force the use of timer mode I guess this means the CPU is not supported: $ cat /dev/oprofile/cpu_type i386/arch_perfmon $ ls /usr/share/oprofile/i386/ athlon core core_2 p4 p4-ht p6_mobile pii piii ppro Workaround (use timer mode): $ lsmod | grep -i oprofile oprofile 50016 1 $ sudo opcontrol --deinit cpu_type 'unset' is not valid you should upgrade oprofile or force the use of timer mode Daemon not running Unloading oprofile module $ lsmod | grep -i oprofile $ sudo modprobe oprofile timer=1 $ sudo opcontrol --init (No error messages.) I don't know which impact the fallback to timer mode has on the performance of oprofile. FYI, from CVS: $ ls oprofile/events/i386/ arch_perfmon athlon atom core core_2 core_i7 CVS nehalem p4 p4-ht p6_mobile pii piii ppro -- oprofile doesn't start https://bugs.launchpad.net/bugs/272209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
