From: Arjan van de Ven <arjan@infradead.org>
To: Aneurin Price <aneurin.price@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression: kernels since 2.6.26 are unusably slow
Date: Sat, 26 Sep 2009 09:20:01 +0200 [thread overview]
Message-ID: <20090926092001.085bd86c@infradead.org> (raw)
In-Reply-To: <501db8660909251509i3eb6cb20i74337928e0708410@mail.gmail.com>
On Fri, 25 Sep 2009 23:09:32 +0100
Aneurin Price <aneurin.price@gmail.com> wrote:
> Hi,
> Every kernel since 2.6.26 has been unusably slow for me - to the
> extent that I initially thought they were hanging on boot. Exactly
> how bad it is seems to vary, but it could take several minutes to
> boot, and then another minute or two to log in (with bash pegging the
> CPU as it loads). Everything seems to need vastly more CPU time than
> usual - it feels a little like I'm using a 486.
means part of memory is uncached.
>
> I've bisected the problem down to commit
> 42651f15824d003e8357693ab72c4dbb3e280836 (x86: fix trimming e820 with
> MTRR holes). Having basically no idea what that means, I thought I'd
> try building a kernel with MTRRs disabled, to see if that would make
> any difference, but no joy.
b0rked MTRRs will do that to you ;-)
>
> Can anyone give me some idea of where to go next, or let me know what
> further information I should provide?
>
one thing to try is enabling CONFIG_MTRR_SANITIZER as config option;
that lets linux rewrite all MTRRs to see if it can puzzle a combination
together that fits all your memory...
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
prev parent reply other threads:[~2009-09-26 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 22:09 Regression: kernels since 2.6.26 are unusably slow Aneurin Price
2009-09-25 22:51 ` Frans Pop
2009-09-26 1:02 ` Aneurin Price
2009-09-26 1:47 ` Yinghai Lu
2009-09-26 2:49 ` Robert Hancock
2009-09-26 22:51 ` Aneurin Price
2009-09-26 7:20 ` Arjan van de Ven [this message]
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=20090926092001.085bd86c@infradead.org \
--to=arjan@infradead.org \
--cc=aneurin.price@gmail.com \
--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