On Wed, 27 Sep 2000, Jaap Schuurmans wrote:
> However, soon, after a few, not always the same number of, transfers,
> something goes astray in the linux-task proper, as indicated by
> the wall-time clock, (seen by eg. xclock -update 1) it stops and
> slowly but shurely linux responsetime is degrading and
> linux stops altogether.
> The real-time module does run on happily, io with our interface
> does not stop, but we can no longer communicate with the rt-module.
I have no idea what happens to the time. Does the system start swapping?
May be your kernel code (or even user) has memory leak? Try to monitor
memory using "free" and "ps -aux" while it slows down.
> i_totalcount++; /* static global, as is i_missed */
Be careful with all counters like this. At 1000 Hz they will wrap around in
25 or 50 days.
--
Tomek
-- [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/
