From: Pavel Machek <pavel@suse.cz>
To: Tom Eastep <teastep@seattlefirewall.dyndns.org>,
"Michael B. Trausch" <fd0man@crosswinds.net>
Cc: Josh Myer <jbm@joshisanerd.com>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Major Clock Drift
Date: Sat, 10 Feb 2001 22:58:07 +0100 [thread overview]
Message-ID: <20010210225807.F7877@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0102040756120.5276-100000@fd0man.accesstoledo.com> <Pine.LNX.4.30.0102040908320.877-100000@wookie.seattlefirewall.dyndns.org>
In-Reply-To: <Pine.LNX.4.30.0102040908320.877-100000@wookie.seattlefirewall.dyndns.org>; from Tom Eastep on Sun, Feb 04, 2001 at 09:18:43AM -0800
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
> system (similar Hw/Sw configuration to yours), a 2.4 kernel "make dep"
> from a vesafb console will cause the system clock to drift 10-12
> seconds.
Hmm, I can make it loose 30 seconds in 12 seconds. Just cat
/etc/termcap. Vesafb does this kind of stuff. [Yes, 3 times slower
clock].
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
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/
next prev parent reply other threads:[~2001-02-11 10:47 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
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 ` Pavel Machek [this message]
2001-02-11 17:07 ` [OT] " 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=20010210225807.F7877@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=fd0man@crosswinds.net \
--cc=jbm@joshisanerd.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox