Re: [As-users] v1.8.11 + toshiba 320CT = 4second freeze every 1020

• Messages sorted by: [ date ][ subject ][ author ]
• Next message: ""
• Previous message: "Re: [As-users] hiding the wharf"

Pls ignore it was a coincidence although quite convincing.

t.

Tim Moore wrote:
> 
> Unfortunately also the same for 2.00.beta4b.  This is with defaults
> ./configure; make; make install; echo afterstep > .xinitrc; startx:
> 
>> server 192.168.1.11, stratum 2, offset 4.161093, delay 0.02583
>> server 192.168.1.10, stratum 3, offset 4.165817, delay 0.02580
>> 28 Jun 14:11:39 ntpdate[21467]: step time server 192.168.1.11 offset 
>> 4.161093 sec
>> server 192.168.1.11, stratum 2, offset 4.161255, delay 0.02583
>> server 192.168.1.10, stratum 3, offset 4.165978, delay 0.02579
>> 28 Jun 14:11:40 ntpdate[21469]: step time server 192.168.1.11 offset 
>> 4.161255 sec
> 
> ** machine freezes here **
> 
>> server 192.168.1.11, stratum 2, offset 8.151905, delay 0.02583
>> server 192.168.1.10, stratum 3, offset 8.156620, delay 0.02579
>> 28 Jun 14:11:41 ntpdate[21471]: step time server 192.168.1.11 offset 
>> 8.151905 sec
>> server 192.168.1.11, stratum 2, offset 8.152067, delay 0.02582
>> server 192.168.1.10, stratum 3, offset 8.156777, delay 0.02582
>> 28 Jun 14:11:43 ntpdate[21473]: step time server 192.168.1.11 offset 
>> 8.152067 sec
> 
> 
> The memory footprint for v1.8.11 is 24MB virtual, 10MB resident, v2beta4 is
> 3x bigger.  Not good for small memory/cpu machines as older laptops.
> 
> Any "look here" suggestions welcome.
> 
> rgds,
> tim.
> 
> Tim Moore wrote:
> 
>> I know this release is not current but would like to fix it since my 
>> laptop has natural limitations (64MB max, Mobile Pentium MMX @266MHz).
>>
>> Somewhere in 1.8.11 is code that causes a precise, repeatable 3.99 
>> second whole system freeze very 1020 seconds no matter how busy or 
>> idle, or task mix.  "whole system" means the entire laptop, including 
>> RTC, is frozen. After the freeze, everything continues as if nothing 
>> happened except that the system time has jumped ahead by 3.990 
>> seconds.  This does not happen on my Asus and Abit based desktops 
>> which all have the same environment.
>>
>> There have never been any problems like dropped packets or data loss, 
>> only  the RTC gaining 4.seconds.  I ran ntpdate to my LAN ntp server 
>> in a 1 second loop to illustrate:
>>
>>> 28 Jun 11:56:52 ntpdate[2780]: adjust time server 192.168.1.11 offset 
>>> 0.002125 sec
>>> 28 Jun 11:56:53 ntpdate[2782]: step time server 192.168.1.11 offset 
>>> 3.992613 sec
>>> ...
>>> 28 Jun 12:13:52 ntpdate[4599]: step time server 192.168.1.11 offset 
>>> 4.003295 sec
>>> 28 Jun 12:13:53 ntpdate[4601]: step time server 192.168.1.11 offset 
>>> 7.993790 sec
>>> ...
>>> 28 Jun 12:30:52 ntpdate[6409]: step time server 192.168.1.11 offset 
>>> 8.004875 sec
>>> 28 Jun 12:30:53 ntpdate[6411]: step time server 192.168.1.11 offset 
>>> 11.995373 sec
>>
>>
>>
>> When I switch to either gnome or kde, no time jumps.  100% repeatable.
>>
>> I am happy to track and fix.  I've looked at lib/{sleep,tick}.c and 
>> can see no obvious 1020s or 4s patterns.  Any suggestions as to where 
>> else to look?
>>
>> Thanks,
>> Tim.
> 
> 
> 

-- 
  | for direct mail add "private_" in front of user name
_______________________________________________
As-users mailing list
As-users@afterstep.org
http://mail.afterstep.org/mailman/listinfo/as-users

• Previous message: "Re: [As-users] hiding the wharf"