From owner-freebsd-current@FreeBSD.ORG  Mon Nov 21 01:45:12 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 13FA716A420
	for <current@freebsd.org>; Mon, 21 Nov 2005 01:45:12 +0000 (GMT)
	(envelope-from thomas@FreeBSD.ORG)
Received: from melamine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org
	[82.225.155.84])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 806E543D55
	for <current@freebsd.org>; Mon, 21 Nov 2005 01:45:11 +0000 (GMT)
	(envelope-from thomas@FreeBSD.ORG)
Received: by melamine.cuivre.fr.eu.org (Postfix, from userid 1000)
	id B22FD5C0E4; Mon, 21 Nov 2005 02:45:04 +0100 (CET)
Date: Mon, 21 Nov 2005 02:45:04 +0100
From: Thomas Quinot <thomas@FreeBSD.ORG>
To: current@freebsd.org
Message-ID: <20051121014504.GA1236@melamine.cuivre.fr.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-message-flag: WARNING! Using Outlook can damage your computer.
User-Agent: Mutt/1.5.9i
Cc: 
Subject: 6.0-BETA5 random freeze with rtc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2005 01:45:12 -0000

On a new Dell Precision 380 box running 6.05-BETA5, I've seen random
freezes (apparently not related to specific activities running on the
machine, which has web and mail servers and also runs an X server) a few
days apart.

On the last two instances, the last message recorded in the logs was the
same:

Nov 21 02:11:22 melamine kernel: rtc: 1000 > kern.hz: Timing will be inaccurate, please increase hz.

and this messages does not occur at any other time, so I suspect it's
related to the freezes I saw. I might have been running mplayer shortly
before the freeze. Could this be related to PR 71536? (i.e. could the
rtc bug cause a freeze, and not only an annoying console message?)

Thomas.