DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently installed a Debian Sarge on a IBM ThinkCentre (Pentium 4 HT).
After having compiling the last kernel (2.6.14.2) with HT module, resolving some latence problems, I've got a strange behavior about the clock system.
My hard one (BIOS) still correct, but the date of the system goes backwards after a random (I think) time.
Here is the result of the date command each "real world" second :
Code:
everest:~# date
dim nov 27 02:24:37 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:37 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:37 CET 2005
everest:~# date
dim nov 27 02:24:37 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:38 CET 2005
everest:~# date
dim nov 27 02:24:39 CET 2005
I can't say why you're seeing the drift in time as reported by the "date" command. Maybe that's just the way it is. I haven't run the date command multiple times per second to see if any of my systems exhibit this drift.
FYI, the "date" command reports the "system clock time". This is seperate from the "real time clock" (a.k.a. "BIOS clock", "hardware clock", "CMOS clock") which is reported by the "hwclock" command. You must be root to run hwclock. Invoke it like "hwclock --show" to read your hardware clock.
When your system boots, the hardware clock is read and the result is used to set the system clock. From then on out the hardware clock is not used. When you shutdown, the system clock data is written back to the hardware clock on many systems.
Other programs like "rdate", "ntpd", "ntpdate", etc. can be used to set your system clock using an external source as reference.
hey! I´m just having the same problem with another IBM ThinCentre (w/ Pentium4 processor) and Linux kernel 2.16.6.1:
The system clock seems to be crazy: Most of the time it is running ok but eventually it slows down, and other times even jumping backwards several seconds. Seems to be a kernel issue
You said you solved the problem removing some modules from the kernel. Can you tell me which ones?
I am running these daemons in the server: postgresql, httpd(apache), svscan(daemonstool), acpid. Could these programs cause the clock behavior?
Well I solved my problem a long time ago, and I didn't notice the fix procedure... But I remember that the solution was in the kernel configuration, not about software.
Have a look at :
- Processor type and features > HPET Timer Support
hey! I´m just having the same problem with another IBM ThinCentre (w/ Pentium4 processor) and Linux kernel 2.16.6.1:
The system clock seems to be crazy: Most of the time it is running ok but eventually it slows down, and other times even jumping backwards several seconds. Seems to be a kernel issue
You said you solved the problem removing some modules from the kernel. Can you tell me which ones?
I am running these daemons in the server: postgresql, httpd(apache), svscan(daemonstool), acpid. Could these programs cause the clock behavior?
thanks a lot,
DukeZer0
Did you figure this one out? I'm having almost the exact same issue...
This is what I did: I rebuild the kernel, making the following changes in the configuration:
Symmetric multi-processing support -> Disabled
SMT (Hyperthreading) scheduler support-> Disabled
Preemption-> No Forced Preemption (Server)
Timer Frequency->100Hz
The kernel was the latest 2.6.? version but this procedure should work with other versions.
I did not remove the ACPI power management options and it worked OK.
This may be a serious kernel issue that the developers are maybe ignoring!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.