On Mon, Jul 27, 2009 at 09:12:34AM +0200, Vlado Držík wrote:
> I'm posting here in hope that someone experienced similiar problem like me.
> I've tried latest kernel 188.8.131.52 on Proliant DL380 G5 and oprofile
> 0.9.4 but I have problem with getting out profiling information.
> The NMI seems not to be triggered for defualt event. I've tried also
> booting kernel with idle=poll.
> In dmesg I can see that actually oprofile has choosen to use NMI:
> oprofile: using NMI interrupt.
> In previous kernels 2.6.18 it seems to be working on 2nd attempt (after
> boot I need to start, stop profiling and then after second start it
> starts generating NMI) but on new one it's not working at all.
> Here is output from oprifle --start -V:
On the DL785 there is a known issue where the HP firmware is itself using
counter 0. HP has acknowledged issue but last I heard, no immediate plan to
fix. Same symptoms you are seeing, NMI==0 in /proc/interrupts.
Counter 0 is running, just not under oprofile control.
Try editing the events file (for your cpu, in /usr/share/oprofile) to use
counter 1 for CPU_CLK_UNHALTED -- i.e remove counter 0 from the set. I don't
believe there is a way to specify this on the command line or in the session