All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Pavel Machek <pavel@suse.cz>
Cc: Hacksaw <hacksaw@hacksaw.org>,
	Tom Eastep <teastep@seattlefirewall.dyndns.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [OT] Major Clock Drift
Date: Sun, 11 Feb 2001 22:05:35 +1100	[thread overview]
Message-ID: <3A8671FF.C390FDCC@uow.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.30.0102040908320.877-100000@wookie.seattlefirewall.dyndns.org> <200102041804.f14I4br22433@habitrail.home.fools-errant.com> <3A7EA9B3.3507DC8D@uow.edu.au>, <3A7EA9B3.3507DC8D@uow.edu.au>; from Andrew Morton on Tue, Feb 06, 2001 at 12:25:07AM +1100 <20010210225851.G7877@bug.ucw.cz>

Pavel Machek wrote:
> 
> Hi!
> 
> > > >I've discovered that heavy use of vesafb can be a major source of clock
> > > >drift on my system, especially if I don't specify "ypan" or "ywrap". On my
> > >
> > > This is extremely interesting. What version of ntp are you using?
> >
> > Is vesafb one of the drivers which blocks interrupts for (many) tens
> > of milliseconds?
> 
> Vesafb is happy to block interrupts for half a second.

And has this been observed to cause clock drift?

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-11 10:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-04  4:32 [OT] Major Clock Drift Josh Myer
2001-02-04  4:42 ` Manfred Bartz
2001-02-04 12:56 ` Michael B. Trausch
2001-02-04 15:18   ` Steve Underwood
2001-02-04 15:31   ` Hacksaw
2001-02-04 23:46     ` Alan Chandler
2001-02-04 17:18   ` Tom Eastep
2001-02-04 18:04     ` Hacksaw
2001-02-04 18:07       ` Tom Eastep
2001-02-05 13:25       ` Andrew Morton
2001-02-10 21:58         ` Pavel Machek
2001-02-11 11:05           ` Andrew Morton [this message]
2001-02-11 11:06             ` Pavel Machek
2001-02-11 11:47               ` Andrew Morton
2001-02-11 12:14               ` Peter Horton
2001-02-11 13:52             ` Chris Wedgwood
2001-02-05  1:18     ` Michael B. Trausch
2001-02-13  3:00       ` george anzinger
2001-02-13  6:51         ` Josh Myer
2001-02-10 21:58     ` [OT] " Pavel Machek
2001-02-11 17:07       ` Alan Cox
2001-02-11 22:29         ` Andrew Morton
2001-02-12  9:48           ` Alan Cox
2001-02-12 10:05             ` Andi Kleen
2001-02-12 10:10               ` Alan Cox
2001-02-12 12:14                 ` James Sutherland
2001-02-12 10:32             ` Pavel Machek
2001-02-12 10:36               ` Alan Cox
2001-02-12 11:38                 ` Andrew Morton
2001-02-13  7:24                   ` Abramo Bagnara
2001-02-10 21:55 ` Pavel Machek

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=3A8671FF.C390FDCC@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=hacksaw@hacksaw.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=teastep@seattlefirewall.dyndns.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 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.