From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755213Ab0IJUMp (ORCPT ); Fri, 10 Sep 2010 16:12:45 -0400 Received: from icebox.esperi.org.uk ([81.187.191.129]:46533 "EHLO mail.esperi.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751209Ab0IJUMn (ORCPT ); Fri, 10 Sep 2010 16:12:43 -0400 To: Jiri Slaby Cc: Thomas Gleixner , Artur Skawina , Venkatesh Pallipadi , Damien Wyart , John Drescher , Suresh Siddha , LKML , "H. Peter Anvin" Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET) References: <87eid282pj.fsf@spindle.srvr.nix> <4C89FD56.6060505@gmail.com> From: Nix Emacs: because editing your files should be a traumatic experience. Date: Fri, 10 Sep 2010 21:12:21 +0100 In-Reply-To: <4C89FD56.6060505@gmail.com> (Jiri Slaby's message of "Fri, 10 Sep 2010 11:41:42 +0200") Message-ID: <87aanp8ije.fsf@spindle.srvr.nix> User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.5-b29 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-DCC-URT-Metrics: spindle 1060; Body=9 Fuz1=9 Fuz2=9 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10 Sep 2010, Jiri Slaby spake thusly: > On 09/10/2010 10:37 AM, Thomas Gleixner wrote: >> HPET provides both functionalities. >> >> The patch you bisected is affecting the clock events part of the >> HPET. So yes, it's not a clock source problem. > > AFAIU, clocksource=jiffies shouldn't fix this issue. If that's the case > we have another 2.6.32->2.6.33 regression (and I will report it What? This is a 2.6.35 regression from 2.6.34 (and all previous kernels). clocksource=jiffies has never yet been mentioned (I could try it, but I think I know what the result would be). 2.6.32 and 2.6.33 both worked fine. > separately). People report the system is unusable (sleepers are not > woken), unless clocksource=jiffies, clocksource=tsc or nolapic_timer is > used or a key pressed (i.e. some HW interrupt): > https://bugzilla.novell.com/show_bug.cgi?id=579932 This is similar, but not identical: this particular bug is only fixed by keypresses in the early stages (in NOHZ mode) and *interferes* with all responsiveness including keystroke response both in NOHZ and !NOHZ mode. It's probably another HPET timer problem, though, but that doesn't mean it necessarily has the same cause.