mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Diederichs <kay.diederichs@uni-konstanz.de>
To: linux-kernel@vger.kernel.org
Subject: stock 2.4.20: loading amd76x_pm makes time jiggle on A7M266-D
Date: Wed, 04 Dec 2002 13:29:55 +0100	[thread overview]
Message-ID: <3DEDF543.51C80677@uni-konstanz.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]

the subject says it all: 

if I use the powersaving module amd76x_pm then the time is not kept. The
hardware is Asus A7M266-D with 2 MP1900 processors, BIOS is 1004 (but I
tried later BIOS versions as well).

Symptoms are:

- ping times vary and there are 'time of day goes back' messages:

64 bytes from xx (1.2.3.4): icmp_seq=4 ttl=64 time=19.549 msec
64 bytes from xx (1.2.3.4): icmp_seq=5 ttl=64 time=2.684 sec
Warning: time of day goes back, taking countermeasures.
64 bytes from xx (1.2.3.4): icmp_seq=6 ttl=64 time=9.799 msec
64 bytes from xx (1.2.3.4): icmp_seq=7 ttl=64 time=88 usec
64 bytes from xx (1.2.3.4): icmp_seq=8 ttl=64 time=20.011 msec
(addresses edited)

- ntpq -p shows a very high jitter:
     remote           refid      st t when poll reach   delay   offset 
jitter
==============================================================================
 loop8.biologie. 134.34.3.18      2 u    6   64   77    0.807  -1920.6
1804.31
 helix1.biologie 134.34.3.18      2 u   13   64   77    0.348  -1914.9
1803.99

- ntpd complains:

Dec  3 19:18:51 turn22 ntpd[730]: synchronisation lost
Dec  3 20:12:15 turn22 ntpd[730]: synchronisation lost
Dec  3 22:50:40 turn22 ntpd[730]: synchronisation lost
Dec  3 23:01:18 turn22 ntpd[730]: synchronisation lost

- the program 'check_time' (attached) which was once posted by R.
Johnson on this list shows that the internal timekeeping is
inconsistent:

Time = 3dedf443
Last = 3dedf440
Time = 3dedf440
Last = 3dedf443
Time = 3dedf443
Last = 3dedf440
Time = 3dedf440
Last = 3dedf443
Time = 3dedf443
Last = 3dedf440
Time = 3dedf440
Last = 3dedf443
Time = 3dedf443
Last = 3dedf440
Time = 3dedf440

Any ideas? Am I really the only one who has seen these problems (on 4
identical machines, BTW)?

Kay
-- 
Kay Diederichs         http://strucbio.biologie.uni-konstanz.de/~kay 
email: Kay.Diederichs@uni-konstanz.de  Tel +49 7531 88 4049 Fax 3183
When replying to my email, please remove the blanks before and after the
"@" !
Fakultaet fuer Biologie, Universitaet Konstanz, Box M656, D-78457
Konstanz

[-- Attachment #2: check_time.c --]
[-- Type: text/plain, Size: 443 bytes --]

#include <stdio.h> 
#include <time.h> 

int main() 
{ 
    time_t tim; 
    time_t last; 
    (void)time(&last); 
    (void)time(&tim); 
    for(;;) 
    { 
        (void)time(&tim); 
        if(tim != last) 
        { 
            if((last +1) != tim) 
            { 
                fprintf(stderr,"Time = %08lx\n", tim); 
                fprintf(stderr,"Last = %08lx\n", last); 
            } 
            last = tim; 
        } 
    } 
} 

             reply	other threads:[~2002-12-04 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 12:29 Kay Diederichs [this message]
2002-12-04 13:45 ` Alan Cox
2002-12-04 13:22   ` Pedro Larroy
2002-12-04 14:33     ` Alan Cox
2002-12-05 10:13   ` Kay Diederichs
2002-12-05 17:39     ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DEDF543.51C80677@uni-konstanz.de \
    --to=kay.diederichs@uni-konstanz.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®