All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oskar Liljeblad" <oskar@osk.mine.nu>
To: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Cc: raw@dslr.net
Subject: clock drift with 2x Promise Ultra133 TX2 (PDC 20269) (again)
Date: Tue, 24 May 2005 18:53:39 +0200	[thread overview]
Message-ID: <20050524165339.GA16577@oskar> (raw)

Problem:
I have two Promise Ultra133 TX2 (PDC 20269) cards, each with two
Maxtor UDMA133 hard drives connected. The system also has another
hard drive connected to the motherboard. A total of five drives.

When I concurrently read from two hard drives connected to
different Promise cards, there is heavy software clock drift.
The software clock runs too fast - approx. a few seconds per
minute during this i/o. To reproduce:

  hwclock --hctosys
  hwclock --show
  date
  dd if=/dev/hde of=/dev/null bs=1M count=7200 &
  dd if=/dev/hdi of=/dev/null bs=1M count=7200 &
  wait
  wait
  hwclock --show
  date

This doesn't happen if I read from two drives connected to the
same card, or one drive connected to the motherboard and one
connected to a Promise card.

I've removed all other PCI devices in the system - problem remains.
I tried different motherboards:

  Asus A7V266-C with AMD AthlonXP 2000+ (i686) - problem occurs
  Asus A7V600-X with AMD Sempron 2600+  (i686) - problem occurs
  Abit KV8 Pro  with AMD Athlon64 3000+ (i686) - problem does not occur!

So what makes the Abit motherboard different?

Regards,

Oskar Liljeblad (oskar@osk.mine.nu)

             reply	other threads:[~2005-05-24 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 16:53 Oskar Liljeblad [this message]
2005-05-24 17:24 ` clock drift with 2x Promise Ultra133 TX2 (PDC 20269) (again) Drew Winstel

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=20050524165339.GA16577@oskar \
    --to=oskar@osk.mine.nu \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raw@dslr.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.