From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756681AbZBFXYn (ORCPT ); Fri, 6 Feb 2009 18:24:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752771AbZBFXYf (ORCPT ); Fri, 6 Feb 2009 18:24:35 -0500 Received: from styx.suse.cz ([82.119.242.94]:41619 "EHLO mail.suse.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751780AbZBFXYf (ORCPT ); Fri, 6 Feb 2009 18:24:35 -0500 Date: Sat, 7 Feb 2009 00:24:33 +0100 (CET) From: Jiri Kosina To: Ben Greear cc: linux-kernel , rusty@rustcorp.com.au Subject: Re: PATCH: Allow user to force 'tsc' to be treated as stable. In-Reply-To: <498C78C9.5090405@candelatech.com> Message-ID: References: <498B42C5.7010905@candelatech.com> <498C78C9.5090405@candelatech.com> User-Agent: Alpine 1.10 (LNX 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 6 Feb 2009, Ben Greear wrote: > > How do you know that the TSC is stable on such system? What was the > > reason for kernel marking it unstable? > I've used it for a timing source in my own modules and it has worked > well. It could still be broken in some way, but if so, I'm not sure how > to detect it. Ingo sent me a program to test the tsc, and at least for > short runs, it showed no problem. > Another person suggested the system might think it is unstable because I > have ACPI disabled in my BIOS and that might cause the kernel not to > have a 'PM timer' that it uses to check the tsc? > Other than that, I have no idea why the kernel thinks the tsc is > unstable. Normally the reason should be indicated by kernel in dmesg output, could you please provide that? Thanks, -- Jiri Kosina SUSE Labs