From: Damien Wyart <damien.wyart@free.fr>
To: Nix <nix@esperi.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?)
Date: Tue, 7 Sep 2010 07:36:00 +0200 [thread overview]
Message-ID: <20100907053600.GA2508@brouette> (raw)
In-Reply-To: <87aanu39ev.fsf@spindle.srvr.nix>
> > I think this is related to what has been discussed in this thread:
> > http://lkml.org/lkml/2010/7/14/11
* Nix <nix@esperi.org.uk> [2010-09-06 21:27]:
> Quite possibly :/ though I'm on x86-64, not x86, and certainly don't
> have kmemleak turne don.
Yes, at first we were talking about x86 and kmemleak but leter on, the
problem seemed more related to x86-64 and the config_no_bootmem option.
> > 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.
Yes, but you seem to get it at each boot and immediately, which was
never my case (don't know about Zeno). With 2.6.35.3 I got it only once
in several days of uptimes and boots.
I hope your specific situation will help isolate the problem...
--
Damien Wyart
next prev parent reply other threads:[~2010-09-07 5:36 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 [this message]
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=20100907053600.GA2508@brouette \
--to=damien.wyart@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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.