From owner-freebsd-stable@FreeBSD.ORG Sun May 23 05:46:25 2004 Return-Path: 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 4509616A4CE for ; Sun, 23 May 2004 05:46:25 -0700 (PDT) Received: from postit.mail.adnap.net.au (postit.mail.adnap.net.au [203.6.132.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB0D343D1F for ; Sun, 23 May 2004 05:46:24 -0700 (PDT) (envelope-from bastill@adam.com.au) Received: from 192.168.1.11 (unknown [202.6.154.199]) by postit.mail.adnap.net.au (Postfix) with ESMTP id 630F51C961 for ; Sun, 23 May 2004 22:15:39 +0930 (CST) From: Brian Astill To: freebsd-stable@FreeBSD.ORG Date: Sun, 23 May 2004 22:13:22 +0930 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200405232213.22361.bastill@adam.com.au> Subject: is microuptime backwards solved? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 May 2004 12:46:25 -0000 I have the Athlon CPU - VIA chipset combination which suffers persistent runaway messages saying "microuptime going backwards" unless APM is removed from the kernel. However, a recent clean install of FBSD 4.9 Release hasn't shown any sign of the problem. Is it fixed or have I somehow been lucky not to produce the trigger? -- Regards, Brian