From owner-freebsd-alpha  Mon Mar  5 10:23:57 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from baron.fujimori.cache.waseda.ac.jp (baron.fujimori.cache.waseda.ac.jp [133.9.152.155])
	by hub.freebsd.org (Postfix) with ESMTP id E837E37B718
	for <freebsd-alpha@freebsd.org>; Mon,  5 Mar 2001 10:23:55 -0800 (PST)
	(envelope-from fujimori@baron.fujimori.cache.waseda.ac.jp)
Received: from baron.fujimori.cache.waseda.ac.jp (localhost [127.0.0.1])
	by baron.fujimori.cache.waseda.ac.jp (8.11.1/8.11.1) with ESMTP id f25INdT38459;
	Tue, 6 Mar 2001 03:23:43 +0900 (JST)
	(envelope-from fujimori@baron.fujimori.cache.waseda.ac.jp)
Message-Id: <200103051823.f25INdT38459@baron.fujimori.cache.waseda.ac.jp>
To: mjacob@feral.com
Cc: freebsd-alpha@freebsd.org
Subject: Re: My list of -CURRENT problems 
In-Reply-To: Your message of "Mon, 05 Mar 2001 09:47:19 PST."
             <Pine.LNX.4.21.0103050923450.16541-100000@zeppo.feral.com> 
Date: Mon, 05 Mar 2001 18:23:39 +0000
From: Yoriaki FUJIMORI <fujimori@baron.fujimori.cache.waseda.ac.jp>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


As for a realtime clock problem, it should persist on many alphapc164,
pc164lx and up1100.  At least in my lab, they all suffer from this.
It was a fun to see `Feb 29, 2000' on all of them. (;_;)

I guess FreeBSD/Alpha alone makes use of mcclock.c.  I could not find
its counterpart in FreeBSD/i386.

Yoriaki Fujimori

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