Re: [rtl] LOCKUP on CPU

[Paolo Mantegazza <mantegazza@aero.polimi.it>]

kumsta christophe wrote:
> 
> 16/05/2001 08:22:53, Paolo Mantegazza <mantegazza@aero.polimi.it> wrote:
> >Unfortunately not. I never noticed the kind of mapping you report on my
> >machines. RTAI-24.1.4 should trap traps and skip the nonmaskable
> >interrupts handling. Such a handling in Linux detects possible CPU locks
> >by checking the number of NMIs against the APIC timers one. You can try
> >also adding: append="nmi_watchdog=0"
> >in LILO to see what happens.
> >It disables lock processing through NMI natively in Linux.
> 
> Hi,
> 
> I'm trying to find where the system lock,
> and I found that it locks in rtai.c, line 532 (hard_lock_all() function)
> in the while loop.
> 
> I get the value :
> cpu_own_irq[HARD_LOCK_IPI].dest_status = 0x000000000
> cpu_online_map = 0x00000003
> global.locked_cpus = 0x80000001
> 
> I agree with dest_status and cpu_online_map, but I don't understand the
> bit 31 in locked_cpus ... is this the 2nd locked cpu ??

There seems to be something related to the mapping of CPUS.
cpu_online_map = 0x00000003 should never produce an 8 in
global.locked_cpus, but 3 at most. At least it has been so till now, on
all the machines I used. It is likely that it must be fixed by a
cascaded double mapping.

The 1 in bit 31 is simply "the lock". 

Ciao, Paolo.