linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Oskar Liljeblad" <oskar@osk.mine.nu>
To: Drew Winstel <DWinstel@Miltope.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bill Davidsen <davidsen@tmr.com>
Subject: Re: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards
Date: Wed, 4 May 2005 22:10:11 +0200	[thread overview]
Message-ID: <20050504201011.GA817@oskar> (raw)
In-Reply-To: <66F9227F7417874C8DB3CEB057727417045155@MILEX0.Miltope.local>

On Tuesday, May 03, 2005 at 13:45, Drew Winstel wrote:
> > Thanks, now it loads correctly. Unfortunately the clock drift still occurs
> > with pata_pdc2027x. I'm guessing here, but can clock drift have anything
> > to do with IRQs? Also, is it normal to see errors in /proc/interrupt?
> 
> I've never noticed any errors before, but that could just be a result of me 
> never actually bothering to look.

Are interrupts errors serious? Can anyone tell? The error count was higher
when I had a fifth PCI card in the computer (natsemi ethernet NIC).
Could there be some kind of PCI card conflict? Maybe I should try to
remove a few of them...

[..]
> Let's do some poking into your kernel config.  What do you have set under 
> "Processor type and features"?

CONFIG_X86_PC=y
CONFIG_MK7=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_HPET_TIMER=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y

In other words, Athlon/Duron/K7 + HPET + Local APIC + IO-Apic
(though I have tried with both XT-PIC and Local APIC, with same
drift).

And no, the clock drift occurs no matter if ntpd is running or not.
It's having a very hard time to syncronize with the remote servers,
because the clock drift is too high. (It also says somewhere in the
NTP documentation that it doesn't handle too high clock drift.)

Regards,

Oskar Liljeblad (oskar@osk.mine.nu)

  reply	other threads:[~2005-05-04 20:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 18:29 clock drift with two Promise Ultra133 TX2 (PDC 20269) cards Drew Winstel
2005-05-04 20:10 ` Oskar Liljeblad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-05 14:45 Drew Winstel
2005-05-03 16:07 Drew Winstel
2005-05-03 17:28 ` Oskar Liljeblad
2005-05-04 17:59   ` Bill Davidsen
2005-05-03 15:13 Drew Winstel
2005-05-03 16:02 ` Oskar Liljeblad
2005-05-03 14:18 Drew Winstel
2005-05-03 14:40 ` Oskar Liljeblad
2005-05-02 19:28 Oskar Liljeblad

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=20050504201011.GA817@oskar \
    --to=oskar@osk.mine.nu \
    --cc=DWinstel@Miltope.com \
    --cc=davidsen@tmr.com \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).