From owner-freebsd-current Sun Feb 16 23:44:13 2003 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 0CDE037B401; Sun, 16 Feb 2003 23:44:13 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6160C43F75; Sun, 16 Feb 2003 23:44:12 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 20A3A536E; Mon, 17 Feb 2003 08:44:09 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org, ia32@freebsd.org Subject: ACPI timer bug From: Dag-Erling Smorgrav Date: Mon, 17 Feb 2003 08:44:09 +0100 Message-ID: User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i386--freebsd) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The clock on my ASUS P5A still runs at double speed unless I have debug.acpi.disable="timer" in loader.conf (as it has for as long as we've had ACPI support). Do any ACPI wizards have any suggestions as to how I could track down the cause of this bug, and hopefully fix it? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message