From: george anzinger <george@mvista.com>
To: "Michael B. Trausch" <fd0man@crosswinds.net>
Cc: Tom Eastep <teastep@seattlefirewall.dyndns.org>,
Josh Myer <jbm@joshisanerd.com>,
linux-kernel@vger.kernel.org
Subject: Re: Major Clock Drift
Date: Mon, 12 Feb 2001 19:00:05 -0800 [thread overview]
Message-ID: <3A88A335.E8E41626@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102042015350.5276-100000@fd0man.accesstoledo.com>
I may be off base here, but the problem as described below does _NOT_
seem to be OT so I removed that from the subject line. A clock drift
change with an OS update is saying _something_ about the OS, not the
hardware. In this case it seems to be the 2.4.x OS that is loosing
time. I suspect the cause is some driver that is not being nice to the
hardware, either by abusing the interrupt off code or locking up the bus
or some such. In any case I think it should _not_ be considered OT.
George
"Michael B. Trausch" wrote:
>
> On Sun, 4 Feb 2001, Tom Eastep wrote:
>
> > Thus spoke Michael B. Trausch:
> >
> > > On Sat, 3 Feb 2001, Josh Myer wrote:
> > >
> > > > Hello all,
> > > >
> > > > I know this _really_ isn't the forum for this, but a friend of mine has
> > > > noticed major, persistent clock drift over time. After several weeks, the
> > > > clock is several minutes slow (always slow). Any thoughts on the
> > > > cause? (Google didn't show up anything worthwhile in the first couple of
> > > > pages, so i gave up).
> > > >
> > >
> > > I'm having the same problem here. AMD K6-II, 450 MHz, VIA Chipset, Kernel
> > > 2.4.1.
> > >
> >
> >
> > The video on this system is an onboard ATI 3D Rage LT Pro; I use vesafb
> > rather than atyfb because the latter screws up X.
> >
>
> I'm not using any framebuffer on my machine (I have an ATI 3D Rage 128
> Pro, myself). I use the standard 80x50 console, and X when I need
> it. I'm about to put Debian on the system and see how that works and if I
> like it, I just got the .ISO of disc 1 downloaded (after about a week) and
> now it's burning. (I hate having a 33.6 connection!)
>
> However the clock drift didn't happen as much, if at all, with 2.2.xx
> kernels. It's kept itself pretty well sane. But now I'm losing something
> on the order of a half hour a week - that didn't happen before.
>
> - Mike
>
> ===========================================================================
> Michael B. Trausch fd0man@crosswinds.net
> Avid Linux User since April, '96! AIM: ML100Smkr
>
> Contactable via IRC (DALNet) or AIM as ML100Smkr
> ===========================================================================
>
> -
> 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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
next prev parent reply other threads:[~2001-02-13 3:03 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 [this message]
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=3A88A335.E8E41626@mvista.com \
--to=george@mvista.com \
--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