From owner-freebsd-ia32 Sun Feb 16 23:44:13 2003 Delivered-To: freebsd-ia32@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-ia32@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-ia32" in the body of the message From owner-freebsd-ia32 Mon Feb 17 1:11:43 2003 Delivered-To: freebsd-ia32@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2FC937B401; Mon, 17 Feb 2003 01:11:42 -0800 (PST) Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id B520E43F3F; Mon, 17 Feb 2003 01:11:41 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.12.6/8.12.6) with ESMTP id h1H9Be6E053536; Mon, 17 Feb 2003 09:11:40 GMT (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h1H9BcOx023882; Mon, 17 Feb 2003 10:11:39 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG, ia32@FreeBSD.ORG Subject: Re: ACPI timer bug From: phk@phk.freebsd.dk In-Reply-To: Your message of "Mon, 17 Feb 2003 08:44:09 +0100." Date: Mon, 17 Feb 2003 10:11:38 +0100 Message-ID: <23881.1045473098@critter.freebsd.dk> Sender: owner-freebsd-ia32@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message , Dag-Erling Smorgrav writes: >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? I don't have any P5A boards, so I'm really at a loss with this one. Basically, something about about ACPI timer does not match spec and I have no idea what it is, or for that matter how to reliably detect it. The best I can suggest is hunting down any errata for the chipset or experimenting.. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia32" in the body of the message