public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Craig-Wood <ncw@axis.demon.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dan Kegel <dank@kegel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: time goes backwards periodically on laptop if booted in low-power mode
Date: Tue, 19 Feb 2002 09:03:21 +0000	[thread overview]
Message-ID: <20020219090321.B366@axis.demon.co.uk> (raw)
In-Reply-To: <20020218213049.A28604@axis.demon.co.uk> <E16cvgK-0006uq-00@the-village.bc.nu>
In-Reply-To: <E16cvgK-0006uq-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Feb 18, 2002 at 09:50:44PM +0000

On Mon, Feb 18, 2002 at 09:50:44PM +0000, Alan Cox wrote:
> > This isn't fixing the root cause of the problem which is interactions
> > between the BIOS power management and the kernel I believe, but it
> > does fix the problem and is really quite cheap so perhaps might be
> 
> do_gettimeofday is still going to give strange results - and consider
> the case where you boot slow and speed up...

This isn't a perfect fix certainly.  Stopping time going backwards
stops the major application breakage though.

> If you can give me the DMI strings for the affected boxes I can add
> them to the DMi tables (see ftp://ftp.linux.org.uk/pub/linux/alan/DMI*)

[sent via private email]

-- 
Nick Craig-Wood
ncw@axis.demon.co.uk

  parent reply	other threads:[~2002-02-19  9:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-17 16:34 time goes backwards periodically on laptop if booted in low-power mode Dan Kegel
2002-02-18 21:30 ` Nick Craig-Wood
2002-02-18 21:50   ` Alan Cox
2002-02-18 21:56     ` Dan Kegel
2002-02-18 22:12       ` time goes backwards periodically on laptop if booted in low-power Alan Cox
2002-02-19  9:03     ` Nick Craig-Wood [this message]
2002-02-18 21:54   ` time goes backwards periodically on laptop if booted in low-power mode Chris Friesen
2002-02-18 22:12     ` Nick Craig-Wood
2002-02-18 23:06       ` Chris Friesen

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=20020219090321.B366@axis.demon.co.uk \
    --to=ncw@axis.demon.co.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dank@kegel.com \
    --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