Bug 3243 - Time runs too slow
Summary: Time runs too slow
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Timers
Classification: Unclassified
Component: Realtime Clock (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: john stultz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-19 04:28 UTC by Ortwin Glück
Modified: 2005-08-16 15:41 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.8.1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
dmesg -s 1000000 (12.52 KB, text/plain)
2004-08-19 09:25 UTC, Ortwin Glück
Details

Description Ortwin Glück 2004-08-19 04:28:18 UTC
Distribution: Gentoo with kernel from kernel.org
Hardware Environment: Acer TM630,  see http://www.odi.ch/prog/tm630/index.php
Software Environment: Gentoo Linux, see http://www.odi.ch/prog/tm630/gentoo.php
Problem Description:
The RTC runs too slow. I get about 50 % of the speed that it should be. Maybe
related to bug #3057

Steps to reproduce:
date
(wait 1 minute)
date

or

sleep 10 (will sleep for 20 seconds)
Comment 1 Damir Perisa 2004-08-19 05:47:50 UTC
with 2.6.8.1-mm1: 
 
[damir@Asteraceae /]$ date; sleep 1; date; sleep 2; date; sleep 3; date  
Thu Aug 19 14:42:34 CEST 2004 
Thu Aug 19 14:42:35 CEST 2004 
Thu Aug 19 14:42:37 CEST 2004 
Thu Aug 19 14:42:40 CEST 2004 
 
so it's either vanilla-specific, or gentoo-problem or Hardware to blame :-) 
Comment 2 Ortwin Glück 2004-08-19 06:11:03 UTC
Damir,

Of course the output of your test is consistent. But you have to compare the
actual time with a real clock (use your wrist watch). All works fine when I use
2.6.6. But since I use 2.6.8.1 my clock is running at 50 % of real speed. I
wouldn't mind if that meant that I could live twice as long :-)

It's not about who to blame. It worked before, and now it's broken. All I
changed is the kernel. If I change back to 2.6.6 the clock runs correct.
Comment 3 Andrew Morton 2004-08-19 09:19:50 UTC
The `dmesg -s 1000000' output would be useful.
Comment 4 Ortwin Glück 2004-08-19 09:25:58 UTC
Created attachment 3532 [details]
dmesg -s 1000000

File as requested. The machine has been running for some hours now.
Comment 5 Bojan Smojver 2004-10-14 04:45:04 UTC
See also Fedora bug:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127235

Same thing but on an HP Pavillion ZE-4201 notebook. 
Comment 6 Ortwin Glück 2004-10-25 16:21:01 UTC
The bug is still present in 2.6.9
Comment 7 Ortwin Glück 2004-12-06 14:02:38 UTC
Still seeing this in 2.6.10-rc3. clock=pmtmr does not help either. Is there
anything I can do to help fixing this?
Comment 8 Ortwin Glück 2005-01-08 03:32:00 UTC
WFM: with 2.6.10 using CONFIG_X86_PM_TIMER it works correctly now.
Comment 9 john stultz 2005-08-09 11:24:57 UTC
Does this problem still exist or is it considered resolved? If it still exists,
does acpi=off change the behaviour?
Comment 10 Ortwin Glück 2005-08-10 10:58:27 UTC
It works now even without CONFIG_X86_PM_TIMER in 2.6.13-rc6.
I tried with 250 and 1000Hz settings, with and without ACPI.
Thanks a lot!
Comment 11 john stultz 2005-08-16 15:41:09 UTC
Considered resovlved by the submitter. Reopen if necessary.

Note You need to log in before you can comment on or make changes to this bug.