From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753231AbYIBEzJ (ORCPT ); Tue, 2 Sep 2008 00:55:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751255AbYIBEy5 (ORCPT ); Tue, 2 Sep 2008 00:54:57 -0400 Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115]:41398 "EHLO mtiwmhc11.worldnet.att.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751137AbYIBEy4 (ORCPT ); Tue, 2 Sep 2008 00:54:56 -0400 Message-ID: <48BCC723.3090007@lwfinger.net> Date: Mon, 01 Sep 2008 23:54:59 -0500 From: Larry Finger User-Agent: Thunderbird 2.0.0.12 (X11/20071114) MIME-Version: 1.0 To: Linus Torvalds CC: Thomas Gleixner , LKML , "Rafael J. Wysocki" , Alok Kataria , Michael Buesch Subject: Re: Regression in 2.6.27 caused by commit bfc0f59 References: <48BB2116.1060904@lwfinger.net> <48BC2A03.9000104@lwfinger.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds wrote: > > On the machine you have trouble with the PIT on, does this thing trigger? > > If it does, that could be a simple way to say whether you prefer PM_TIMER > over PIT. > > For me, even on a modern machine, I get a pit_count of 46321, which > matches the "about one microsecond for an ISA/LPC read" timing pretty > well. What do you get? On the problem AMD K6, the count is 29411. On my almost new AMD Turion 64 X2 that runs at 2.0 GHz, the value was 31401. A cutoff value of 25000 may be a bit close. That machine says that it calibrates against the PM_TIMER, but cat /sys/devices/...../current_clocksource returns hpet. Larry