[Linux-users] the system clock stopped?!?

[Lonni J Friedman]

To return to this thread, i'm now seeing this same problem on a
*second* system running Fedora 7 (x86).  So this is most definitely
not a hardware problem.  The 2nd system does not have the same
motherboard as the 1st, so its not even a motherboard specific
problem.  The only commonality between the two systems is that they
both have AMD CPUs, however one system is dual core, the other is not.

Again, this problem only seems to happen if the system is sitting idle
(like over the past 3 day weekend).  Beyond that, I can't find any way
to deterministically trigger the behavior.  Surely, I can't be in some
weird Bermuda triangle where my systems hit this weirdness?

On 8/27/07, Leon Goldstein <metapsych at earthlink.net> wrote:
> Lonni J Friedman wrote:
>
> <snip>
>
> >On 8/27/07, Leon Goldstein <metapsych at earthlink.net> wrote:
> >
> >
> >>I'd start by replacing the CMOS battery.  I experienced similar oddities
> >>after manually setting the BIOS clock to Bush time.  I had to keep
> >>resetting the clock until I replaced the battery.
> >>
> >>
> >
> >To the best of my knowledge the CMOS battery only plays a role when
> >the system is powered off and/or doesn't have external power.
> >However, even if it were the CMOS battery, why would the time in the
> >BIOS be correct?
> >
> >
> >
> >
> Your original post did not make it clear that the BIOS clock is keeping
> good time.
> In any event, it only costs a couple of $ to get a new battery and rule
> it out as a suspect.
>
> --
> Leon A. Goldstein
>
> Powered by Libranet 2.8 Debian Linux
> System LI
>
>

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama at gmail.com
LlamaLand                       http://netllama.linux-sxs.org