From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "set_rtc_mmss: can't update from m to n" cluttering my logs
Date: Fri, 22 Sep 2006 15:02:42 +0200 [thread overview]
Message-ID: <20060922150242.4a46287b@localhost.localdomain> (raw)
In-Reply-To: <20060918192431.42ec5df5.akpm@osdl.org>
El Mon, 18 Sep 2006 19:24:31 -0700
Andrew Morton <akpm@osdl.org> escribió:
> On Mon, 18 Sep 2006 13:13:03 +0200
> Alejandro Riveira Fernández <ariveira@gmail.com> wrote:
>
> > Hi, i'm using a 2.6.18-rc7 in an 3880+ X2 AM2 with an uli 1697 chipset
> > and i'm seeing this on the logs
> >
> > Sep 18 12:49:34 localhost last message repeated 17 times
> > Sep 18 12:49:40 localhost last message repeated 3 times
> > Sep 18 12:49:44 localhost kernel: set_rtc_mmss: can't update from 110 to 49
> > Sep 18 12:49:57 localhost last message repeated 8 times
> > Sep 18 12:50:01 localhost kernel: set_rtc_mmss: can't update from 110 to 50
> > Sep 18 12:50:32 localhost last message repeated 17 times
> > Sep 18 12:50:41 localhost last message repeated 4 times
> > Sep 18 12:50:42 localhost kernel: set_rtc_mmss: can't update from 111 to 50
>
> That code hasn't really changed in a long time. Are you able to determine
> approximately which kernel version introduced this problem?
i can no know because i changed hardware with that kernel already
installed :(.
Btw the messages are gone with 2.6.18 final and i suspect that
everything comes down to a buggy bios
[You can ignore the rest of msg it is just a rant]
Sometimes it messes up system date and time forcing fsck in hd's and
other headaches. i see a msg at boot time about bios not reserving
e820 memory and PCI: mmio disabled or something like that. i can not
tell for sure because oddly enough the msg does not end up in logs ??)
>
> Thanks.
Thanks to you for the time you invested in this useless msg and big
thanks for your work in Linux
---
> All is fine except that I can reliably "oops" it simply by trying to
> read from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
--Alan Cox LKML-December 08,2000
prev parent reply other threads:[~2006-09-22 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 11:13 "set_rtc_mmss: can't update from m to n" cluttering my logs Alejandro Riveira Fernández
2006-09-19 2:24 ` Andrew Morton
2006-09-22 13:02 ` Alejandro Riveira Fernández [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=20060922150242.4a46287b@localhost.localdomain \
--to=ariveira@gmail.com \
--cc=akpm@osdl.org \
--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