Re: 2.6.29-rc4 regression (was: Re: 2.6.28-rc9: oprofileregression)

[Robert Richter]

Tim,

still, I can not reproduce this with my tests with v2.6.29-rc4. The
regression on the systems I have runs fine on rc4. On the system you
have, is commit b99170288421c79f0c2efa8b33e26e65f4bb7fb8 the first bad
one? If so, I will split the patch into smaller pieces to find the
change that introduces the bug.

-Robert

On 11.02.09 20:51:17, Tim Blechmann wrote:
> i am not sure, whether it is related to my problem with 2.6.28, but
> running oprofile on kernel 2.6.29-rc4 (today's linus/master to be
> exact), i do not get _any_ NMI:
> 
> tim@thinkpad:~$ sudo opcontrol -s
> Using 2.6+ OProfile kernel interface.
> Using log file /var/lib/oprofile/samples/oprofiled.log
> Daemon started.
> Profiler running.
> tim@thinkpad:~$ cat /proc/interrupts |grep NMI
> NMI:          0          0   Non-maskable interrupts
> tim@thinkpad:~$ sudo opcontrol -d
> tim@thinkpad:~$ cat /proc/interrupts |grep NMI
> NMI:          0          0   Non-maskable interrupts
> 
> dmesg tells me:
> oprofile: using NMI interrupt.
> 
> best, tim
> 
> -- 
> tim@xxxxxxxxxx
> http://tim.klingt.org
> 
> When you open windows, bugs get in.
> 



-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@xxxxxxx

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/