Re: 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?)

[Nix]

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/