From: Ian Stirling <root@mauve.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Laptop system clock slow after suspend to disk. (2.4.0-test9/hinote VP)
Date: Thu, 21 Dec 2000 02:26:12 +0000 (GMT) [thread overview]
Message-ID: <200012210226.CAA20107@mauve.demon.co.uk> (raw)
In-Reply-To: <E148tqH-0002JQ-00@the-village.bc.nu> from "Alan Cox" at Dec 21, 2000 12:44:19 AM
I've not noticed this on earlier kernel versions, is there something
silly I'm missing that's making my DEC hinote VP (p100 laptop)s
system clock slow by a factor of five or so after resume?
Not the CPU or cmos clock, only the system clock.
Thoughts welcome.
-
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/
next prev parent reply other threads:[~2000-12-21 2:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 16:18 iptables: "stateful inspection?" Michael Rothwell
2000-12-20 16:25 ` Michael H. Warfield
2000-12-20 16:30 ` Michael Rothwell
2000-12-20 16:51 ` David Lang
2000-12-20 17:13 ` Michael H. Warfield
2000-12-20 17:52 ` Michael Rothwell
2000-12-20 18:08 ` Michael H. Warfield
2000-12-20 18:38 ` Michael H. Warfield
2000-12-20 17:08 ` Michael H. Warfield
2000-12-20 20:45 ` Alan Cox
2000-12-20 20:51 ` Michael Rothwell
2000-12-20 22:02 ` Dax Kelson
2000-12-21 0:44 ` Alan Cox
2000-12-21 2:26 ` Ian Stirling [this message]
2000-12-21 22:05 ` Laptop system clock slow after suspend to disk. (2.4.0-test9/hinote VP) Keith Owens
2000-12-21 2:37 ` iptables: "stateful inspection?" Michael Rothwell
2000-12-21 7:00 ` George
[not found] ` <20001222140517.A30215@convergence.de>
2000-12-22 15:42 ` Michael Rothwell
2000-12-21 2:46 Laptop system clock slow after suspend to disk. (2.4.0-test9/hinote VP) Douglas Gilbert
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=200012210226.CAA20107@mauve.demon.co.uk \
--to=root@mauve.demon.co.uk \
--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
all inboxes | Powered by JetHome®