From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: set_rtc_mmss: can't update from 0 to 59
Date: Mon, 18 Dec 2000 08:48:19 -0800 [thread overview]
Message-ID: <20001218084819.A17221@one-eyed-alien.net> (raw)
In-Reply-To: <UTC200012181310.OAA170929.aeb@aak.cwi.nl>
In-Reply-To: <UTC200012181310.OAA170929.aeb@aak.cwi.nl>; from Andries.Brouwer@cwi.nl on Mon, Dec 18, 2000 at 02:10:32PM +0100
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Honestly, this is the best solution I've heard. It seems that the message
is somewhat bogus, anyway, seeing as how this message is somewhat "normal"
and just represents the occasional occurance of a fast cmos clock with
xntpd and running the code near the top of the hour.
Matt
On Mon, Dec 18, 2000 at 02:10:32PM +0100, Andries.Brouwer@cwi.nl wrote:
> From mdharm@ziggy.one-eyed-alien.net Mon Dec 18 04:47:51 2000
>
> > so if your cmos time is 0.001 sec ahead of your system time
> > then around the hour you'll see
> > set_rtc_mmss: can't update from 0 to 59
>
> but, the question is, how do we fix this?
>
> Put #if 0 ... #endif around the printk.
>
> Andries
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
Oh BAY-bee.
-- Dust Puppy to Greg
User Friendly, 12/13/1997
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-12-18 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-18 13:10 Andries.Brouwer
2000-12-18 16:48 ` Matthew Dharm [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-17 20:54 Andries.Brouwer
2000-12-18 3:47 ` Matthew Dharm
2000-12-18 8:46 ` Russell King
2000-12-19 21:13 ` Oliver Xymoron
2000-12-19 22:25 ` Russell King
2000-12-19 22:53 ` Oliver Xymoron
2000-12-21 9:28 ` Paul Gortmaker
2000-12-21 10:07 ` Russell King
2000-12-17 20:32 Matthew Dharm
2000-12-18 13:11 ` Matthias Andree
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=20001218084819.A17221@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=Andries.Brouwer@cwi.nl \
--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®