From owner-freebsd-questions@FreeBSD.ORG  Thu Feb  6 15:25:19 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CF8FA7CE
 for <freebsd-questions@freebsd.org>; Thu,  6 Feb 2014 15:25:19 +0000 (UTC)
Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net
 [IPv6:2001:44b8:8060:ff02:300:1:6:4])
 by mx1.freebsd.org (Postfix) with ESMTP id 5B05C1239
 for <freebsd-questions@freebsd.org>; Thu,  6 Feb 2014 15:25:19 +0000 (UTC)
Received: from ppp103-111.static.internode.on.net (HELO
 lillith-iv.ovirt.dyndns.ws) ([150.101.103.111])
 by ipmail04.adl6.internode.on.net with ESMTP; 07 Feb 2014 01:55:17 +1030
X-Envelope-From: ws@au.dyndns.ws
X-Envelope-To: freebsd-questions@freebsd.org
Received: from [172.17.17.136] (ws@predator-ii.buffyverse [172.17.17.136])
 by lillith-iv.ovirt.dyndns.ws (8.14.5/8.14.5) with ESMTP id s16FP3aX055676;
 Fri, 7 Feb 2014 01:55:04 +1030 (CST) (envelope-from ws@au.dyndns.ws)
Subject: Re: Invalid time in real time clock
From: Wayne Sierke <ws@au.dyndns.ws>
To: Christian Weisgerber <naddy@mips.inka.de>
In-Reply-To: <lclnst$1fu$1@lorvorc.mips.inka.de>
References: <lcj2jj$2bu$1@lorvorc.mips.inka.de>
 <lcjpn2$1a07$1@lorvorc.mips.inka.de>  <lclnst$1fu$1@lorvorc.mips.inka.de>
Content-Type: text/plain; charset="ASCII"
Date: Fri, 07 Feb 2014 01:55:03 +1030
Message-ID: <1391700303.2036.32.camel@predator-ii.buffyverse>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (lillith-iv.ovirt.dyndns.ws [172.17.17.142]);
 Fri, 07 Feb 2014 01:55:04 +1030 (CST)
X-Scanned-By: MIMEDefang 2.73 on 172.17.17.142
X-Scanned-By: SpamAssassin 3.003002(2011-06-06)
X-Scanned-By: ClamAV
X-Spam-Score: -2.9 () ALL_TRUSTED,BAYES_00
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 15:25:19 -0000

On Sun, 2014-02-02 at 15:23 +0000, Christian Weisgerber wrote:
> Christian Weisgerber <naddy@mips.inka.de> wrote:
> 
> > > atrtc0: WARNING: Battery failure indication
> > > Invalid time in real time clock.
> > > Check and reset the date immediately!
> > > 
> > > Incongruously, the RTC time is actually correct.  Well, off by a
> > > minute or so.  Clearly the new battery is good.
> > 
> > Turns out I misunderstood this.  I thought the system time was still
> > set from the RTC despite the warning.  It isn't.
> 
> Still, booting into the BIOS shows that the RTC keeps up, so it
> shouldn't be a battery problem.  I cleared the RTC memory, set the
> date and time in the BIOS again, but I still get the warning and
> FreeBSD ignores the RTC.  It looks like the RTCSD_PWR bit is stuck
> and there is no way to reset it.

Hi Christian,

When you say "the RTC keeps up" do you mean that the RTC keeps time when
mains power is removed - i.e. power cord unplugged for a "reasonable"
length of time? If the RTC doesn't "survive" complete removal of power
then you may want to double-check the CMOS jumper and battery.


Wayne