Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261855AbVASTMW (ORCPT ); Wed, 19 Jan 2005 14:12:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261857AbVASTMW (ORCPT ); Wed, 19 Jan 2005 14:12:22 -0500 Received: from ppp-217-133-42-200.cust-adsl.tiscali.it ([217.133.42.200]:22583 "EHLO dualathlon.random") by vger.kernel.org with ESMTP id S261855AbVASTMM (ORCPT ); Wed, 19 Jan 2005 14:12:12 -0500 Date: Wed, 19 Jan 2005 20:12:08 +0100 From: Andrea Arcangeli To: Tony Lindgren Cc: Pavel Machek , George Anzinger , john stultz , Zwane Mwaikambo , Con Kolivas , Martin Schwidefsky , linux-kernel@vger.kernel.org Subject: Re: [PATCH] dynamic tick patch Message-ID: <20050119191208.GC12647@dualathlon.random> References: <20050119000556.GB14749@atomide.com> <20050119094342.GB25623@elf.ucw.cz> <20050119171323.GB14545@atomide.com> <20050119174858.GB12647@dualathlon.random> <20050119181947.GF14545@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050119181947.GF14545@atomide.com> X-AA-GPG-Key: 1024D/68B9CB43 13D9 8355 295F 4823 7C49 C012 DFA1 686E 68B9 CB43 X-AA-PGP-Key: 1024R/CB4660B9 CC A0 71 81 F4 A0 63 AC C0 4B 81 1D 8C 15 C8 E5 X-Cpushare-GPG-Key: 1024D/4D11C21C 5F99 3C8B 5142 EB62 26C3 2325 8989 B72A 4D11 C21C X-Cpushare-SSL-SHA1-Cert: 38 12 CD 76 E4 82 94 AF 02 0C 0F FA E1 FF 55 9D 9B 4F A5 9B X-Cpushare-SSL-MD5-Cert: ED A5 F2 DA 1D 32 75 60 5E 07 6C 91 BF FC B8 85 User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 15 On Wed, Jan 19, 2005 at 10:19:47AM -0800, Tony Lindgren wrote: > If you have a chance, can you please provide me with some more info > on your system, see my recent reply to Pavel in this thread for the It's a normal UP athlon 1ghz, it should be quite widespread hardware. I know at least another system that had the problem of system time going in the future with 2.6 at the same rate of mine. Still it could be an hardware issue after all if nobody else can reproduce it. At HZ=100 the system time is again perfectly accurate like in 2.4, so probably at least the PIT is ok. - 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/