From owner-freebsd-questions  Tue Mar  6  8:17:57 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from freyr.cba.ualr.edu (freyr.cba.ualr.edu [144.167.120.20])
	by hub.freebsd.org (Postfix) with ESMTP id 6F1E637B719
	for <freebsd-questions@freebsd.org>; Tue,  6 Mar 2001 08:17:54 -0800 (PST)
	(envelope-from joe@freyr.cba.ualr.edu)
Received: by freyr.cba.ualr.edu (Postfix, from userid 1000)
	id 94A4D180; Tue,  6 Mar 2001 10:18:34 -0600 (CST)
Date: Tue, 6 Mar 2001 10:18:33 -0600
From: "Joseph E. Royce" <joe@freyr.cba.ualr.edu>
To: "John E.P. Hynes" <john@hytronix.com>
Cc: freebsd-questions@freebsd.org
Subject: Re: Alpha PC164 Clock not Y2K Compliant?
Message-ID: <20010306101833.A11049@freyr.cba.ualr.edu>
References: <01030610160500.11112@tatewaki>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <01030610160500.11112@tatewaki>; from john@hytronix.com on Tue, Mar 06, 2001 at 10:16:05AM -0500
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 06, 2001 at 10:16:05AM -0500, John E.P. Hynes wrote:
> Hello All,
> 
> I'm new to the list (but I've been using FreeBSD on a number of machines for 
> quite some time.)
> 
> I recently installed FreeBSD 4.2-RELEASE on an Alpha for the first time (all 
> my other boxes are x86) and I noticed that if I use "date" to set the clock 
> to March 6, 2001, after the next reboot the kernel complains that the clock 
> lost 365 days, and indeed, the time/day is correct, but the year shows up as 
> 2000.  Currently, I just run ntpdate before ntpd loads, and all is well.
> 
> Is there a known Y2K issue with the clock chips on the PC164 Motherboard, or 
> could there be an issue with the way the "date" command updates the hardware 
> clock?
> 
> -John
>
It not a Y2K issue but a SRM quirk, maybe? Excerpt taken from
/usr/src/release/texts/alpha/HARDWARE.TXT:

SRM quirks:
PC164 the SRM sometimes seems to loose its variable settings. 
"For PC164, current superstition says that, to avoid losing settings,
you want to first downgrade to SRM 4.x and then upgrade to a 5.x"
One sample error that was observed was: "ERROR: ISA table corrupt!".
A sequence of a downgrade to SRM4.9, an 'isacfg -init' and an 'init'
made the problem go away. Some PC164 owners report they have never seen 
the problem.

I have never had any problems with mine.

HTH, Joe R.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message