From: Nix <nix@esperi.org.uk>
To: Damien Wyart <damien.wyart@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?)
Date: Mon, 06 Sep 2010 21:27:04 +0100 [thread overview]
Message-ID: <87aanu39ev.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <20100906053255.GA23340@brouette> (Damien Wyart's message of "Mon, 6 Sep 2010 07:32:55 +0200")
On 6 Sep 2010, Damien Wyart told this:
> I think this is related to what has been discussed in this thread:
> http://lkml.org/lkml/2010/7/14/11
Quite possibly :/ though I'm on x86-64, not x86, and certainly don't
have kmemleak turne don.
> I've not seen the problem with 2.6.35.4 yet, and only once with
> 2.6.35.3. Zeno said it disappeared for him when he started to use
> 2.6.35-stable.
Argh.
> So if you can reproduce it quite easily, I guess bisection (even
> painful) will be the best way to get (hopefuly) an idea of where the
> problem might come from...
'Quite easily' is not quite true. It does not show up in qemu -kernel.
It does not show up if you boot straight to an emergency boot shell
in the initramfs (I was trying to avoid activating the RAID arrays).
So I guess it's a full-blown boot each time, which is made pointlessly
difficult by the fact that the rpc.mountd on my NFS server is acting up,
giving me -ESTALE half the time for an initial mount (??!!!) and thus
totally buggering up my client system whenever I reboot. So I may have
to debug *that* first. What fun.
But I'll get around to it.
next prev parent reply other threads:[~2010-09-06 20:27 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 [this message]
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
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=87aanu39ev.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=damien.wyart@free.fr \
--cc=linux-kernel@vger.kernel.org \
/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