From: Eric Seppanen <eds@reric.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: via timer/clock problem workaround
Date: Thu, 23 May 2002 14:15:28 -0500 [thread overview]
Message-ID: <20020523141528.A28780@reric.net> (raw)
In-Reply-To: <20020522221859.A24041@reric.net> <3CECB24E.D41B1527@mvista.com> <20020523103340.A27767@reric.net> <3CED076C.20C24B23@mvista.com> <20020523113943.A28069@reric.net> <3CED1AF4.7170970@mvista.com>
Note that most of this thread occurred off-list and this is the tail end.
It looks as though the timer tick interrupt is going away. If true,
that's well outside the scope of what can be detected/repaired from inside
do_gettimeofday(). So the workarounds posted on this list that I've seen
look like the wrong approach. That includes the fix that's in 2.4.18.
On Thu, May 23, 2002 at 09:38:12AM -0700, george anzinger wrote:
> Eric Seppanen wrote:
> > george anzinger wrote:
> > > The unfortunate thing about the fix is that execution of the
> > > detection code requires some one to request the time of
> > > day. This, of course, could be delayed by an arbitrary
> > > time, depending on system activity.
> >
> > Good point. Looking at it from that perspective, it may be a waste of
> > time to put fixes in do_gettimeofday(). A dead timer is pretty serious,
> > and I can't think of a simple way to detect it.
On this note, if anybody has any hints on why the timer may be dying, how
to debug it, or better places to detect/fix it, I'd be grateful.
prev parent reply other threads:[~2002-05-23 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 3:18 via timer/clock problem workaround Eric Seppanen
2002-05-23 9:11 ` george anzinger
[not found] ` <20020523103340.A27767@reric.net>
[not found] ` <3CED076C.20C24B23@mvista.com>
[not found] ` <20020523113943.A28069@reric.net>
2002-05-23 16:38 ` george anzinger
2002-05-23 19:15 ` Eric Seppanen [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=20020523141528.A28780@reric.net \
--to=eds@reric.net \
--cc=linux-kernel@vger.kernel.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