Menu
▾
▴
[coLinux-devel] [ colinux-Bugs-1780633 ] Clock drift every 5 seconds
|
From: SourceForge.net <no...@so...> - 2010-05-20 10:19:26
|
Bugs item #1780633, was opened at 2007-08-23 22:24 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1780633&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Clock drift every 5 seconds Initial Comment: Hello, I installed both coLinux 0.6.4 and 0.7.1 and the Debian 4.0 image from sourceforge. The problem remains: Every 5 seconds, the system clock is increased by 8 hours, 35 minutes and 45 seconds. Example: debian:~# while sleep 1; do date; done Sat Aug 25 10:44:38 CEST 2007 Sat Aug 25 10:44:39 CEST 2007 Sat Aug 25 10:44:40 CEST 2007 Sat Aug 25 10:44:41 CEST 2007 Sat Aug 25 19:20:26 CEST 2007 Sat Aug 25 19:20:27 CEST 2007 Sat Aug 25 19:20:28 CEST 2007 Sat Aug 25 19:20:29 CEST 2007 Sat Aug 25 19:20:30 CEST 2007 Sun Aug 26 03:56:27 CEST 2007 Sun Aug 26 03:56:28 CEST 2007 Sun Aug 26 03:56:30 CEST 2007 Sun Aug 26 03:56:31 CEST 2007 Sun Aug 26 03:56:32 CEST 2007 Sun Aug 26 12:32:17 CEST 2007 Sun Aug 26 12:32:18 CEST 2007 Sun Aug 26 12:32:19 CEST 2007 Sun Aug 26 12:32:20 CEST 2007 Sun Aug 26 12:32:21 CEST 2007 Sun Aug 26 21:07:54 CEST 2007 Sun Aug 26 21:08:19 CEST 2007 [...] debian:~# uname -a Linux debian 2.6.12-co-0.7.1 #1 Sun Dec 31 20:25:16 UTC 2006 i686 GNU/Linux The host is an AMD Athlon 64 3200+ system with 1 GB RAM, SATA harddisk and Windows XP Home SP2. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-05-20 10:19 Message: Update: I've tried the same kernel and system on a native XP SP2: It works perfectly. The problem with my previous test may be the fact that my XP runs in VirtualBox? (Too much virtualisation) , SP3? ---------------------------------------------------------------------- Comment By: vAx (re-vax) Date: 2010-05-17 17:18 Message: Same problem with my gentoo and coLinux: 2.6.33-co-0.8.0 #1 PREEMPT Sun Mar 21 19:46:28 UTC 2010 i686 Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz GenuineIntel GNU/Linux ( >=2.6.27 kernel is required for UDEV to work. ) all is running on XP SP3 (uptodate). I've tried to solve with ntpd, but it dosen't. It's a shame, time is so important for my project (file server). How can I help? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-02-07 10:21 Message: Logged In: NO Hello, some months ago I wrote this bug report. Now I found out the the problem only occurs under Windows XP Home SP2. With SP1, the clock behaves normal. I tested both the OEM Version of Windows XP deliviered with the PC, and a vanilla Windows XP CD from Microsoft. No matter which Install medium was used, installation of SP2 breaks the clock under coLinux. Installing SP2 also leads to two other oddities on this machine. The machine does not fully power down when shutting down under Windows; you have to press the power button for 5 seconds to shut down entirely. And no VMware product is working under SP2; I've tested Workstation, Player, and Server. With SP1, all theres products run fine. However, Innotec VirtualBox runs fine under SP2. Not nice, but I can live with it. Thanks to all who helped. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-09-02 20:54 Message: Logged In: YES user_id=579204 Originator: NO Reinstalling windows would not help, I'm afraid. coLinux time base use an windows software timer for the HZ value (100ms). This should work in all cases. You can running native linux. Ok. Please compaire the kernel bootmessages (dmesg). Have the native kernel any special hacks for this cpu? Compair also the /proc/cpuinfo. Any difference with the TSC? Please enable colinux-debug after boot, for 10 seconds, than stop it with CTRL-C and view into the file. coLinux would print, if detect some problems. colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml Hope you will see and problems. Have you tried to go into runlevel S ("init s" after boot). Can you check any other time recources? wath does /proc/uptime? The same as you see on "top". PS: German is no problem. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-08-26 20:35 Message: Logged In: NO Hallo, thanks for your hints. Unfortunately, they did not help. :-( I have now tried daemons-0.8.0-20070810.zip together with vmlinux-2.6.22-co-0.8.0-20070808.zip . Same problem. On another machine (Celeron, 512 MB, SATA HD) with Windows XP Professional SP2, the same coLinux+kernel combination works without problems. The file /etc/adjtime containes "0.0 0 0.0". There is no process under the linux system which could change the time. I have stopped all processes, and also tried the kernel parameter "init=/bin/bash", but the time drift remains. I can hardly believe that the host CPU is broken, because native Linux runs fine on the system. Maybe the Windows XP should be reinstalled... Btw, the technical details of the PC are listed here: http://www.heise.de/ct/hintergrund/meldung/45580 The page is in German, but the table at the end should be readable without German language skills. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-08-24 10:45 Message: Logged In: YES user_id=579204 Originator: NO All kernels before 2.6.22 have the same source code for time (coLinux 0.7.1 and before). Perhaps the 2.6.22 solved it? The code for timer is completely new there. But, I'm afraid, it is some in the configuration or with the host cpu. Please check that /etc/adjtime has "0 0 0" in the first line. >From coLinux no such process is known to change the time all 5 seconds. Has you a process, what does such? Try to start colinux in the lowest runlevel "init s" or "init 1". Than, check the time warp again. PS: Please use the tested snapshot http://www.colinux.org/snapshots/, not the autobuilds. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-08-24 05:42 Message: Logged In: NO Those versions are both horribly out of date. If you're interested in using colinux, you really should subscribe to the mailing list at https://lists.sourceforge.net/lists/listinfo/colinux-devel (about 5 messages per week). That's where the new releases are available. The latest version is this one: http://sourceforge.net/mailarchive/forum.php?thread_name=20070810085406.4E919112C6A%40HNE-LX.terminal&forum_name=colinux-devel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1780633&group_id=98788 |