Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964891AbVLJDLK (ORCPT ); Fri, 9 Dec 2005 22:11:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964900AbVLJDLK (ORCPT ); Fri, 9 Dec 2005 22:11:10 -0500 Received: from smtp2.Stanford.EDU ([171.67.16.125]:44489 "EHLO smtp2.Stanford.EDU") by vger.kernel.org with ESMTP id S964891AbVLJDLI (ORCPT ); Fri, 9 Dec 2005 22:11:08 -0500 Date: Fri, 9 Dec 2005 19:10:39 -0800 (PST) From: Fernando Pablo Lopez-Lezcano X-X-Sender: nando@cmn37.stanford.edu To: john stultz cc: linux-kernel@vger.kernel.org, , Thomas Gleixner , Steven Rostedt , Fernando Pablo Lopez-Lezcano , Ingo Molnar Subject: Re: 2.6.14-rt22 (acpi_pm vs tsc vs BIOS) In-Reply-To: <1134181887.4002.7.camel@leatherman> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1712 Lines: 39 On Fri, 9 Dec 2005, john stultz wrote: > On Fri, 2005-12-09 at 17:21 -0800, Fernando Lopez-Lezcano wrote: > > On Fri, 2005-12-09 at 15:48 -0800, Fernando Lopez-Lezcano wrote: > > > Hi all, I'm running 2.6.14-rt22 and just noticed something strange. I > > > have not installed it in all machines yet, but in some of them (same > > > hardware as others that seems to work fine) the TSC was selected as the > > > main clock for the kernel. Remember this is one of the Athlon X2 > > > machines in which the TCS's drift... > > > > > > dmesg shows this: > > > PM-Timer running at invalid rate: 2172% of normal - aborting. > > > > > > and after that the tsc is selected as the timing source. > > > Time: tsc clocksource has been installed. > > > > > > The strange thing is that this is the same hardware as on other > > > machines. > > > > Aha! Yes but no. The BIOS makes a difference. The first BIOS that has > > support for the X2 processors on this particular motherboard works fine > > with regards to the acpi_pm clock source, subsequent ones make linux say > > things like: > > PM-Timer running at invalid rate: 2159% of normal - aborting. > > and then tsc is selected as the clock source... > > So you're saying the newer BIOS detects the PM timer as running too fast > or is it the older ones? Yes, newer ones are apparently broken. This is a GA-K8NS Ultra-939 (NForce3), acpi_pm is recognized with BIOS F7, gives an error with F8 or F9... -- Fernando - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/