Hi

I have recompiled kernel with OPROFILE disabled. I am sending in
attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and
netconsole log. Lockup in the lock is software made with ./lockup.
The kernel still locks 4-5minutes after boot without any further
messages (waited more than 2 minutes). Any ideas?


Rok


Ingo Molnar wrote:
quoted text
> could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI 
> watchdog?
> 
> how does /proc/interrupts look like shortly after bootup? Does a simple 
> "intentional lockup" piece of code, which provokes a hard lockup from 
> user-space, get properly zapped by the NMI watchdog (within a minute or 
> so):
> 
> the NMI watchdog should produce a console message similar to:
> 
>  BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers:
>  ...
> 
> ( if you test ./lockup and get the message properly then i'd suggest a 
>   new reboot - i think we inhibit further console output after an NMI 
>   printout. )
> 
> 	Ingo
> 
>