From: Brad Douglas <brad@neruo.com>
To: Andrew Morton <morton@nortelnetworks.com>
Cc: ebuddington@wesleyan.edu, linux-kernel@vger.kernel.org
Subject: Re: time drift and fb comsole activity
Date: 28 Feb 2001 16:43:49 -0800 [thread overview]
Message-ID: <20010301004657Z129389-407+1@vger.kernel.org> (raw)
In-Reply-To: <3A9D8BC4.45009947@asiapacificm01.nt.com>
In-Reply-To: <20010228170030.C2122@sparrow.nad.adelphia.net> <3A9D8BC4.45009947@asiapacificm01.nt.com>
On 28 Feb 2001 23:37:40 +0000, Andrew Morton wrote:
> Eric Buddington wrote:
> >
> > I know this has been reported on the list recently, but I think I can
> > provide better detail. I'm running 2.4.2 with atyfb on a K6-2/266
> > running at 250. This system has no history of clock problems.
> >
> > adjtimex-1.12 --compare gives me "2nd diff" readings of -0.01 in quiescent
> > conditions.
> >
> > flipping consoles rapidly cboosts this number to -3 or -4.
> >
> > catting the full documentation to ntpd (seemed appropriate) gives me
> > "2nd diff" numbers a little over 34. If I read the numbers correctly,
> > 47 seconds of CMOS time passed while the system clock only passed 13
> > seconds.
> >
> > The processor and the CMOS clock were moving at zero velocity relative
> > to each other, and were both in normal Earth gravity.
>
> The kernel blocks interrupts during console output. fbdev
> consoles are slow. Net result: many lost timer interrupts.
>
> I'm working on it. Slowly. Should have something next week.
You may want to check out the linuxconsole project on Sourceforge. I
believe one of their goals is to remove/minimize the console lock...
Brad Douglas
brad@neruo.com
http://www.linux-fbdev.org
prev parent reply other threads:[~2001-03-01 0:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 22:00 Eric Buddington
2001-02-28 23:37 ` Andrew Morton
2001-02-28 23:50 ` Cort Dougan
2001-03-01 0:01 ` Alan Cox
2001-02-28 23:59 ` Cort Dougan
2001-03-01 0:04 ` Alan Cox
2001-03-01 0:04 ` Cort Dougan
2001-03-01 0:43 ` Brad Douglas [this message]
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=20010301004657Z129389-407+1@vger.kernel.org \
--to=brad@neruo.com \
--cc=ebuddington@wesleyan.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=morton@nortelnetworks.com \
/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®