* Bad clock? battery?
@ 2003-10-15 15:20 Robert L. Harris
0 siblings, 0 replies; only message in thread
From: Robert L. Harris @ 2003-10-15 15:20 UTC (permalink / raw)
To: Linux-Kernel
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
A system of mine just started producint this:
2003-10-15 07:00:19 kernel: set_rtc_mmss: can\'t update from 59 to 0
Apparant Cause :
potential problem in the hardware's real time clock (at least, as far as I
can tell from the messags. The kernel is trying to update the hardware
clock with the correct time and getting errors)
I haven't been able to find much else yet. Any chance this could be
caused by a dead/dying motherboard battery or is it likely the timeclock
is dying? This should be a Tyan 2466 motherboard and one of about 50
identicle systems out in production and the only one producing this
error.
Thanks,
Robert
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-10-15 15:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-15 15:20 Bad clock? battery? Robert L. Harris
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®