From owner-freebsd-current Sun Mar 5 13:47:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01766 for current-outgoing; Sun, 5 Mar 1995 13:47:49 -0800 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01749 for ; Sun, 5 Mar 1995 13:47:44 -0800 Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id QAA17529 for current@freebsd.org; Sun, 5 Mar 1995 16:47:38 -0500 Received: by starkhome.cs.sunysb.edu (8.6.10/1.34) id HAA00193; Sun, 5 Mar 1995 07:36:33 -0500 Date: Sun, 5 Mar 1995 07:36:33 -0500 From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark) Message-Id: <199503051236.HAA00193@starkhome.cs.sunysb.edu> To: current@FreeBSD.org Subject: Invalid time in real-time clock Sender: current-owner@FreeBSD.org Precedence: bulk A freshly compiled kernel from this morning's sup reports the following: Invalid time in real time clock: check and reset the date immediately. However, the date appears to have been correctly initialized. I never got this before. The message comes from i386/isa/clock.c, but this doesn't appear to have been changed recently. What gives? - Gene Stark