From owner-freebsd-current Fri Aug 3 2:31: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 935FA37B405; Fri, 3 Aug 2001 02:31:07 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f739XTg00741; Fri, 3 Aug 2001 02:33:30 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030933.f739XTg00741@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Daniel Rock Cc: Mike Smith , current@freebsd.org Subject: Re: ACPI: Clock problems in -current In-reply-to: Your message of "Wed, 01 Aug 2001 21:00:06 +0200." <3B6851B6.4BD4EDD7@t-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 02:33:29 -0700 From: Mike Smith 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 > I forgot: Even if I define CLK_USE_*_CALIBRATION (and get no error messages > after defining debug.acpi.timer_test), the Off/2 error still persist. Ok. I'm going to revert to the "safe" read code in a few minutes. Can you update and let me know if you're still wildly off? I'm having a hard time believing that your timer is really running at double pace, but I guess anything is possible. If it still does, I'll add some code to check it with the TSC. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message