[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [kumsta christophe <christophe.kumsta@free.fr>] (fwd)
- To: rtl@rtlinux.org
- Subject: BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [kumsta christophe <christophe.kumsta@free.fr>] (fwd)
- From: Der Herr Hofrat <der.herr@hofr.at>
- Date: Wed, 16 May 2001 18:28:46 +0200 (CEST)
>From owner-rtl Wed May 16 03:11:16 2001
Received: from postfix1-2.free.fr (postfix1-2.free.fr [213.228.0.130])
by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f4G9BFr05078
for <rtl@rtlinux.org>; Wed, 16 May 2001 03:11:15 -0600
Received: from KUMSTA_XE3 (nas-cbv-1-6-61.dial.proxad.net [213.228.6.61])
by postfix1-2.free.fr (Postfix) with SMTP
id 938041028C7; Wed, 16 May 2001 11:06:30 +0200 (CEST)
Date: Wed, 16 May 2001 11:08:54 +0100
To: Paolo Mantegazza <mantegazza@aero.polimi.it>, rtlinux <rtl@rtlinux.org>
From: kumsta christophe <christophe.kumsta@free.fr>
Subject: Re: [rtl] LOCKUP on CPU
X-Mailer: Opera 5.00 build 828
X-Priority: 3 (Normal)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20010516090630.938041028C7@postfix1-2.free.fr>
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 ??
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.