mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Mark Cooke <mpc@star.sr.bham.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible critical VIA vt82c686a chip bug
Date: Mon, 30 Oct 2000 16:23:45 +0100	[thread overview]
Message-ID: <20001030162345.A5469@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0010261555250.15391-200000@pc24.sr.bham.ac.uk> <Pine.LNX.4.21.0010301130060.28728-200000@pc24.sr.bham.ac.uk>
In-Reply-To: <Pine.LNX.4.21.0010301130060.28728-200000@pc24.sr.bham.ac.uk>; from mpc@star.sr.bham.ac.uk on Mon, Oct 30, 2000 at 11:36:10AM +0000

On Mon, Oct 30, 2000 at 11:36:10AM +0000, Mark Cooke wrote:

> As a followup - I modified your reset patch to work with 2.2.x, and in
> doing so, I noticed that it is only the slow get time of day (not
> using TSC) that is affected.  I have my kernel compiled with TSC, so 
> my apparent clock jumping (screen saver starting at odd times) is
> probably not actually due to the timer messing up. (Though I did
> manage initially to convince myself that it had made a difference.
> Good ol' placebo effect in action).
> 
> I guess that the other places where the timer's used could be causing
> some trouble though.  As I have TSC enabled, any reset of the timer's
> not going to get corrected by the patch.
> 
> I'll throw together a program to check for gettimeofday jumping when
> I next have a few minutes to chase this further.

I don't think so. If you check the code paths more closely, you'll see
that the timer is used even in the fast TSC case, the error causes by
too big 'count' variable propagates up to the TSC routine. That's where
I started hunting for the bug.

So no, it wasn't a placebo effect. Put a printk() in the fix statement
to see if it's triggered.

-- 
Vojtech Pavlik
SuSE Labs
-
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:[~2000-10-30 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0010261555250.15391-200000@pc24.sr.bham.ac.uk>
     [not found] ` <Pine.LNX.4.21.0010301130060.28728-200000@pc24.sr.bham.ac.uk>
2000-10-30 15:23   ` Vojtech Pavlik [this message]
2000-10-30 15:31     ` Mark Cooke

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=20001030162345.A5469@suse.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpc@star.sr.bham.ac.uk \
    /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®