From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 18:45:05 2006 Return-Path: X-Original-To: freebsd-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 0CE5F16A4DE; Fri, 7 Jul 2006 18:45:04 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A43E43D45; Fri, 7 Jul 2006 18:45:04 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 6291811514; Fri, 7 Jul 2006 14:44:25 -0400 (EDT) Message-ID: <44AEABC8.5010609@rogers.com> Date: Fri, 07 Jul 2006 14:45:28 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Martin Nilsson References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADDEE0.7080805@gneto.com> In-Reply-To: <44ADDEE0.7080805@gneto.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:45:05 -0000 Martin Nilsson wrote: > I have the same board and the same problem with 6.1. I have tested > CURRENT a bit on the box and I can't remember seeing these errors there. > > The errors are present in both i386 and amd64 versions of FreeBSD, > they are very easy to reproduce just boot and buildworld and you get > at ton of these. I have lots of these boards not in production, so I'm > happy to test patches if needed. Oddly enough i have the same board in production, but it's using a 2.6GHz CPU, and running in amd64 mode. It does not exhibit this problem. I wonder if its a bios issue, this new board has 1.1a, the amd64 box may be a little older. Whats your bios version?