On Mon, 30 May 2005, Pierluigi Di Lorenzo wrote:

hi everybody
in one of my Trustix server I have this problem from 2-3 days.

[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:41 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:41 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:42 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:41 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:42 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:41 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:41 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:40 CEST 2005
[EMAIL PROTECTED] /var/log# date
Mon May 30 08:20:41 CEST 2005

but hwclock works:

[EMAIL PROTECTED] /var/log# hwclock
Mon May 30 11:20:40 2005  0.903354 seconds


what can be happened?

I don't have an answer to your request, but I can give you my experiences.

Searching in the mailing list archive, you can find that some month ago (09-11/2004) I have the same (or similar) problem on a IBM DeskTop used ad Linux gateway. Reinstalled TSL 2.0/2.1/2.2 without solve the problem. I have found hints about acpi, but in my tests don't help. I noticied /proc/sys/net/ipv4/ip_conntrack_max was very "populated" when the box have problems.
I have solved replacing the box with different hardware (an old IBM server).

I have also noticied that TSL 2.1/2.2 give me problems in VmWare virtual machine (lost at last 5-15 mins/day).
But I haven't find a solution (a part activating ntpd).
No similar problem on TSL 1.5/2.0.

I hope this can be useful to someone that hav more skill that me ... ;-)

Regards, B.

_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss

Reply via email to