From: John Drescher <drescherjm@gmail.com>
To: Nix <nix@esperi.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Venkatesh Pallipadi <venki@google.com>,
Damien Wyart <damien.wyart@free.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
Date: Thu, 9 Sep 2010 20:08:28 -0400 [thread overview]
Message-ID: <AANLkTincCptbDWrXup9aej1YJuHXgy2xriyZgdW9ceFD@mail.gmail.com> (raw)
In-Reply-To: <87iq2e8o80.fsf@spindle.srvr.nix>
On Thu, Sep 9, 2010 at 7:57 PM, Nix <nix@esperi.org.uk> wrote:
> On 10 Sep 2010, John Drescher spake thusly:
>
>>> John, Damien, you seem to be experiencing this: are you using HPET as
>>> your clocksource? Do you also have ICH10 82801JIs, or is this more
>>> widespread?
>>>
>> I am not using hpet as my clocksource.
>>
>> jmd1 ~ # uname -a
>> Linux jmd1 2.6.35-std160-amd64 #2 SMP Fri Aug 13 18:42:02 UTC 2010
>> x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
>> jmd1 ~ # cat /sys/devices/system/clocksource/clocksource0/current_clocksource
>> tsc
>
> Hm, interesting. Perhaps the HPET is needed anyway? (That would explain
> why my other system, with identical specs to those above and using tsc
> as clocksource, was seeing intermittent problems in this area.)
>
> But 82801JI looks like a common factor.
Now the interesting part. I switched to acpi_pm 10 to 15 minutes ago
using the following command
jmd1 ~ # echo acpi_pm
>/sys/devices/system/clocksource/clocksource0/current_clocksource
and it was still slow. But now its running fast (well at lest as far
as I can tell via a ssh connection).
John
next prev parent reply other threads:[~2010-09-10 0:14 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 [this message]
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
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=AANLkTincCptbDWrXup9aej1YJuHXgy2xriyZgdW9ceFD@mail.gmail.com \
--to=drescherjm@gmail.com \
--cc=damien.wyart@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.