george.priv@[EMAIL PROTECTED]
wrote:
> On Apr 7, 10:43 am, george.p...@[EMAIL PROTECTED]
wrote:
>> On Apr 7, 3:25 am, "Dmitry A. Kazakov" <mail...@[EMAIL PROTECTED]
>
>> wrote:
>>
>> > On Sun, 6 Apr 2008 20:10:38 -0700 (PDT), george.p...@[EMAIL PROTECTED]
wrote:
>> > > On Apr 5, 6:51 pm, george.p...@[EMAIL PROTECTED]
wrote:
>>
>> > [...]
>>
>> > > with Ada.Calendar;
>> > > use Ada.Calendar;
>>
>> > I don't know the implementation of, but Ada.Calendar is a political
time,
>> > influenced by the time synchronization stuff. What happens if you
replace
>> > it by Ada.Real_Time?
>>
>> > --
>> > Regards,
>> > Dmitry A. Kazakovhttp://www.dmitry-kazakov.de
>>
>> It may worth trying and I will set this up running at first
>> op****tunity, but I think since it is a particular computer system/OS
>> combination it should eliminate "political" issue since all systems
>> are in one time zone and all synced from the same time server. So far
>> I saw that happening only on one system with Server 2003. Similar
>> hardware running Debian is doing fine. Other machines running Windows
>> XP and Vista (Notebook) went for 32 hours now and doing fine. All
>> workstations at my place are the same - that limits my sample pool. I
>> also do repeat run on failed machine to see if there will be
>> consistency in times.
>>
>> Regards,
>>
>> George Privalov
>
> As soon as I posted that message, my XP workstation failed. But time
> is now off forward 2 seconds after 30.5 hours. So drama is not over
> yet.
>
> Actual Delay: 10.000123715, Running (h): 30.430967673
> Actual Delay: 10.000125595, Running (h): 30.433745487
> Actual Delay: 10.000125257, Running (h): 30.436523299
> Actual Delay: 10.000124860, Running (h): 30.439301112
> Actual Delay: 10.000124743, Running (h): 30.442078925
> Actual Delay: 12.000310334, Running (h): 30.445412345
> Actual Delay: 12.000189837, Running (h): 30.448745732
> Actual Delay: 12.000190605, Running (h): 30.452079118
> Actual Delay: 12.000190805, Running (h): 30.455412505
> Actual Delay: 12.000191032, Running (h): 30.458745892
> Actual Delay: 12.000189268, Running (h): 30.462079278
> Actual Delay: 12.000190642, Running (h): 30.465412665
> Actual Delay: 12.000190666, Running (h): 30.468746051
> Actual Delay: 12.000190224, Running (h): 30.472079438
> Actual Delay: 12.000190730, Running (h): 30.475412825
>
> George
I remember some delay-related bug in the windows version of 3.15p. In my
code
it manifested as tasks blocking for unexpectedly long times (usually hours
instead of milliseconds). I thought it had been fixed long ago, and
certainly
your symptoms are different.
However, in case it has any relation, here's one (it seems it's partial,
google
lost track) thread dealing with it. There may be more, and there was a
patch
somewhere.
http://groups.google.com/group/comp.lang.ada/browse_frm/thread/5e062f5bcdb88fd8/94576cccaf04d9de?tvc=1&q=mosteo+bug#94576cccaf04d9de
|
