public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Artur Skawina <art.08.09@gmail.com>,
	Venkatesh Pallipadi <venki@google.com>,
	Damien Wyart <damien.wyart@free.fr>,
	John Drescher <drescherjm@gmail.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
Date: Fri, 10 Sep 2010 21:12:21 +0100	[thread overview]
Message-ID: <87aanp8ije.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <4C89FD56.6060505@gmail.com> (Jiri Slaby's message of "Fri, 10 Sep 2010 11:41:42 +0200")

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.

  parent reply	other threads:[~2010-09-10 20:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05  0:51 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?) Nix
2010-09-06  5:32 ` Damien Wyart
2010-09-06 20:27   ` Nix
2010-09-07  5:36     ` Damien Wyart
2010-09-08 21:24   ` Nix
2010-09-08 21:35     ` John Drescher
2010-09-08 22:25       ` Nix
2010-09-09 22:34     ` [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET) Nix
2010-09-09 23:44       ` John Drescher
2010-09-09 23:57         ` Nix
2010-09-10  0:08           ` John Drescher
2010-09-10  0:14             ` John Drescher
2010-09-10  0:59       ` Artur Skawina
2010-09-10  5:36         ` Damien Wyart
2010-09-10  7:42         ` Nix
2010-09-10  7:47           ` Damien Wyart
2010-09-10  8:37           ` Thomas Gleixner
2010-09-10  9:41             ` Jiri Slaby
2010-09-10 13:22               ` Artur Skawina
2010-09-10 20:13                 ` Nix
2010-09-10 20:12               ` Nix [this message]
2010-09-14 10:09             ` Thomas Gleixner
2010-09-14 20:17               ` Nix
2010-09-14 22:18                 ` Thomas Gleixner
2010-09-14 22:23                 ` Artur Skawina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87aanp8ije.fsf@spindle.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=art.08.09@gmail.com \
    --cc=damien.wyart@free.fr \
    --cc=drescherjm@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venki@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox