FS#5429 - System time problem

Attached to Project: Arch Linux
Opened by Nicolas (Elrohir) - Thursday, 21 September 2006, 16:55 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hello,

I have a bug since february, and ntpd doesn't solve it...
Me and other experience some disfunction with the system clock it can loose or gain up to 10 minutes per day.

This bug doesn't appears in other distributions (Debian, Gentoo).

Ntpd i correctly configured and doesn't synchronise the clock. However, I can do a ntpdate with a cron...

I don't think it's serious for the distribution to leave this bug...

Elrohir
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Tuesday, 06 February 2007, 12:06 GMT
Reason for closing:  None
Comment by Nicolas (Elrohir) - Friday, 22 September 2006, 09:06 GMT
I try to compile a kernel 2.6.18 : there is no time problem.

I conclude the problem is due kernel26 or kenel26beyond...
Comment by Tobias Powalowski (tpowa) - Friday, 22 September 2006, 09:31 GMT
does this mean 2.6.18 in testing fixes this issue?
Comment by Nicolas (Elrohir) - Friday, 22 September 2006, 14:56 GMT
No, except if I compil the kernel myself...
Comment by Tobias Powalowski (tpowa) - Friday, 22 September 2006, 14:57 GMT
now the master question what is different?
Comment by Nicolas (Elrohir) - Friday, 22 September 2006, 14:59 GMT
I don't know.
I compiled a very simple kernel 2.6.18.

What I know is if I use kernel26 or kernel26beyond, there is the clock problem.

I'm not the one.

My configuration :
Athlon2800+
Asus A7N8X
Comment by Tobias Powalowski (tpowa) - Friday, 22 September 2006, 15:01 GMT
post your config, then i can diff it
EDIT:
also post lsmod output and dmesg
Comment by Nicolas (Elrohir) - Friday, 22 September 2006, 15:07 GMT
with the package kernel26 (time problem) or my perso kernel (no problem) ?
Comment by Tobias Powalowski (tpowa) - Friday, 22 September 2006, 15:08 GMT
if you want to do me a big favour,
attach the config from your own kernel,
attach dmesg output with stock and own kernel
attach lsmod output with stock and own kernel
:)
Comment by Nicolas (Elrohir) - Friday, 22 September 2006, 16:13 GMT
No problem ;-)
(application/octet-stream)    stock_lsmod (2.7 KiB)
(application/octet-stream)    stock_dmesg (18.2 KiB)
(application/octet-stream)    new_dmesg (15 KiB)
(application/octet-stream)    new_config (38 KiB)
(application/octet-stream)    new_lsmod (0.1 KiB)
Comment by Tobias Powalowski (tpowa) - Saturday, 23 September 2006, 06:56 GMT
phew, it's difficult to say what really changes it, because you are so far away from the standard config :/
Comment by Nicolas (Elrohir) - Saturday, 23 September 2006, 07:38 GMT
About my new config ? :-/
It's the .config default file, I've just hard compiled FS and IDE/SATA.
Comment by Tobias Powalowski (tpowa) - Saturday, 23 September 2006, 07:43 GMT
you use a differnt hz, no smp other acpi options etc.
attached is a diff the + is what you set the - is stock, if you have much time to debug this i would suggest to play with these options, and tell us what causes it :)
   important.diff (7.6 KiB)
Comment by Nicolas (Elrohir) - Saturday, 23 September 2006, 13:59 GMT
I want to help you, but, I can't do it... I'm not a "master" in compiling kernel :-/
Comment by Woody Gilk (Shadowhand) - Tuesday, 10 October 2006, 04:50 GMT
Maybe it's "rtc" support. Just a random guess.
Comment by Roman Kyrylych (Romashka) - Monday, 13 November 2006, 22:18 GMT
Have you tried different clock= kernel options?
Comment by Woody Gilk (Shadowhand) - Monday, 13 November 2006, 23:04 GMT
Have you tried using openntpd instead of ntp?
Comment by Roman Kyrylych (Romashka) - Saturday, 16 December 2006, 20:23 GMT
status of this one?
Comment by Nicolas (Elrohir) - Sunday, 17 December 2006, 14:23 GMT
The kernel stock a already the same problem... So I use always my own kernel wich I compiled myself and no problem...

I will never use stock kernel Arch because there were nobody to fix (or search) this problem ;-)
Comment by Roman Kyrylych (Romashka) - Monday, 18 December 2006, 09:32 GMT
nobody to fix (or search) this problem??? hmmm...

Have you tried to diff stock and your kernel configs to see what difference fixed your problem?

Loading...