BOUNCE rtl@rtlinux.org: Approval required: (fwd)

[Der Herr Hofrat <der.herr@hofr.at>]

>From owner-rtl Thu Aug  2 10:39:02 2001
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [12.13.237.21])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f72Gd2s17443
	for <rtl@fsmlabs.com>; Thu, 2 Aug 2001 10:39:02 -0600
Received: from slb-av-01.boeing.com ([129.172.13.4])
	by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id JAA27330
	for <rtl@fsmlabs.com>; Thu, 2 Aug 2001 09:35:57 -0700 (PDT)
Received: from stl-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-01) with ESMTP id JAA13547
	for <rtl@fsmlabs.com>; Thu, 2 Aug 2001 09:36:28 -0700 (PDT)
Received: from xch-pssbh-01.nw.nos.boeing.com (xch-pssbh-01.nw.nos.boeing.com [192.42.227.32])
	by stl-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id f72GXKa11225
	for <rtl@fsmlabs.com>; Thu, 2 Aug 2001 11:33:20 -0500 (CDT)
Received: by xch-pssbh-01.nw.nos.boeing.com with Internet Mail Service (5.5.2650.21)
	id <P0FAWJPZ>; Thu, 2 Aug 2001 09:33:18 -0700
Message-ID: <949ACC17102DD045AAB154CEB75A7EC402B10D6A@xch-nw-21.nw.nos.boeing.com>
From: "Basham, Richard R" <Richard.Basham@PSS.Boeing.com>
To: "'rtl@fsmlabs.com'" <rtl@fsmlabs.com>
Subject: RE: [rtl] Re: RE: keyboard freeze with one percent CPU load
Date: Thu, 2 Aug 2001 09:33:09 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain

Marvin,

Thanks for the reply, that clears a few things up in my mind.  Now I understand the symptoms better.  Unfortunately, I do not know of a more elegant solution.  Maybe someone at FSM Labs can explain the intended method for handling this and/or the observed behavior.

regards,

Rich



-----Original Message-----
From: Marvin Germain [mailto:megermain@earthlink.net]
Sent: Wednesday, August 01, 2001 11:00 AM
To: rtl@rtlinux.org
Subject: [rtl] Re: RE: keyboard freeze with one percent CPU load


Hi, Rich.

    I calculated the CPU load by timing the ISR (50 us, not ms),

and comparing this with the time between interrupts.  The computations

are actually commented out for now, so all the second module is doing

is pthread_suspend_np().  The operating system is definately not frozen,

because I can regain control by pulling the plug on the external

data clock, thereby stopping the interrupts.  I think the problem is

with the scheduler, based on the results in my follow-up post. To re-

iterate, I put a call to rtl_schedule() in a periodic task, which

seemed to fix the problem.  This implies that user-space tasks are

simply not being scheduled when the interrupts arrive once every five

mill-seconds.

Marvin
-
*********************************************
*         Dr. Marvin E. Germain             *
*         Zygo Corporation - Tucson AZ      *
*         megermain@earthlink.net           *
*********************************************


----- End of forwarded message from owner-rtl@fsmlabs.com -----
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail majordomo@rtlinux.org OR
echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.org
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/

----- End of forwarded message from owner-rtl@fsmlabs.com -----