From owner-freebsd-stable@FreeBSD.ORG Wed Aug 24 14:19:43 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B938116A41F for ; Wed, 24 Aug 2005 14:19:43 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DF3343D45 for ; Wed, 24 Aug 2005 14:19:43 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 102 invoked from network); 24 Aug 2005 14:19:42 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 24 Aug 2005 14:19:42 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 288DC2E; Wed, 24 Aug 2005 10:19:41 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Jason References: <20050823135800.GA10072@monsterjam.org> From: Lowell Gilbert Date: 24 Aug 2005 10:19:40 -0400 In-Reply-To: <20050823135800.GA10072@monsterjam.org> Message-ID: <44wtmbto1v.fsf@be-well.ilk.org> Lines: 13 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: stable@freebsd.org Subject: Re: calcru: runtime went backwards and hard lockup in 5.4-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Aug 2005 14:19:43 -0000 Jason writes: > and I see > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE > but this info seems to only apply to 4.x. Not really, but the values are making *huge* jumps back and forth, so it's not just a matter of missing some interrupts in your case. > Is this really a problem? how can I squelch it? It does seem to be a problem. It may be a hardware problem with your timekeeping source. Try changing the timecounter.