From owner-freebsd-questions@FreeBSD.ORG  Thu Aug  5 16:45:00 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 33F1C16A4CE
	for <freebsd-questions@freebsd.org>;
	Thu,  5 Aug 2004 16:45:00 +0000 (GMT)
Received: from coverity.dreamhost.com (coverity.dreamhost.com [66.33.192.105])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2AA1F43D2F
	for <freebsd-questions@freebsd.org>;
	Thu,  5 Aug 2004 16:45:00 +0000 (GMT)
	(envelope-from tedu@coverity.com)
Received: from coverity.com (dsl093-171-098.sfo4.dsl.speakeasy.net
	[66.93.171.98])
	by coverity.dreamhost.com (Postfix) with ESMTP id 65A5690887
	for <freebsd-questions@freebsd.org>;
	Thu,  5 Aug 2004 09:44:59 -0700 (PDT)
Message-ID: <411262E6.3020102@coverity.com>
Date: Thu, 05 Aug 2004 09:40:06 -0700
From: Ted Unangst <tedu@coverity.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: clock problem
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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, 05 Aug 2004 16:45:00 -0000

I have an IBM thinkpad T40 running FreeBSD 4.10.  It does not support 
apm, and acpi made the system very flaky.  This hardly matters, since 
the BIOS suspend function still works.  However, when I open the lid, 
the system clock is set to the same time it was when I closed the lid. 
ie, close lid at 6:30pm, open lid at 9:00am next morning, and 'date' 
tells me the time is 6:31pm yesterday.

This seems to be a matter of the system time relying on timecounters 
only.  How do I disable this behavior, or have it use the CMOS clock?

Interesting sysctl values:
machdep.disable_rtc_set: 0
machdep.wall_cmos_clock: 1
machdep.i8254_freq: 1193182
machdep.tsc_freq: 1594833412
kern.timecounter.method: 0
kern.timecounter.hardware: TSC