16/05/2001 08:22:53, Paolo Mantegazza <[EMAIL PROTECTED]> 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 ??
As you suggested, I add "nmi_watchdog=0" and that removed the CPULOCK
seg.fault but the system still blocked in the while loop.
This is normal, because the while condition is never verified.
So I'm now looking for the global.locked_cpus ...
Chris.
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
