Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946171AbWJ0HdW (ORCPT ); Fri, 27 Oct 2006 03:33:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946172AbWJ0HdW (ORCPT ); Fri, 27 Oct 2006 03:33:22 -0400 Received: from mail.gmx.net ([213.165.64.20]:63644 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S1946171AbWJ0HdW (ORCPT ); Fri, 27 Oct 2006 03:33:22 -0400 X-Authenticated: #14349625 Subject: Re: [2.6.18-rt7] BUG: time warp detected! From: Mike Galbraith To: john stultz Cc: LKML In-Reply-To: <1161929321.6102.2.camel@Homer.simpson.net> References: <1161847210.32585.14.camel@Homer.simpson.net> <1161897932.960.49.camel@localhost> <1161927940.6039.6.camel@Homer.simpson.net> <1161929321.6102.2.camel@Homer.simpson.net> Content-Type: text/plain Date: Fri, 27 Oct 2006 08:04:53 +0000 Message-Id: <1161936293.6249.8.camel@Homer.simpson.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1730 Lines: 42 On Fri, 2006-10-27 at 06:08 +0000, Mike Galbraith wrote: > On Fri, 2006-10-27 at 05:45 +0000, Mike Galbraith wrote: > > On Thu, 2006-10-26 at 14:25 -0700, john stultz wrote: > > > On Thu, 2006-10-26 at 07:20 +0000, Mike Galbraith wrote: > > > > $subject happened on my single P4/HT box sometime after resume from > > > > disk. Hohum activity: I had just read lkml and was retrieving latest > > > > glibc snapshot when I noticed the trace. I also noticed that the kernel > > > > decided to use pit instead of tsc. > > > > > > Huh. Was the PIT selected before or after the resume from disk? > > > > Both. If I don't specify tsc, it chooses pit. I just removed freshly > > added clocksource=tsc, rebooted, and I'm back on pit again. > > (hm. virgin 2.6.18 selects tsc properly... will rummage through rt7) #include #ifndef CONFIG_HIGH_RES_TIMERS /* lower the rating if we already know its unstable: */ if (check_tsc_unstable()) clocksource_tsc.rating = 50; #else /* * Mark TSC unsuitable for high resolution timers. TSC has so * many pitfalls: frequency changes, stop in idle ... When we * switch to high resolution mode we can not longer detect a * firmware caused frequency change, as the emulated tick uses * TSC as reference. This results in a circular dependency. * Switch only to high resolution mode, if pm_timer or such * is available. */ clocksource_tsc.rating = 50; clocksource_tsc.is_continuous = 0; #endif - 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/