All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Aneurin Price <aneurin.price@gmail.com>
Cc: linux-kernel@vger.kernel.org, Yinghai Lu <yinghai.lu@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Regression: kernels since 2.6.26 are unusably slow
Date: Sat, 26 Sep 2009 00:51:32 +0200	[thread overview]
Message-ID: <200909260051.34541.elendil@planet.nl> (raw)
In-Reply-To: <501db8660909251509i3eb6cb20i74337928e0708410@mail.gmail.com>

Adding maintainers involved with the commit in CC.

Aneurin Price 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.
> 
> 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.
> 
> Can anyone give me some idea of where to go next, or let me know what
> further information I should provide?

Let's start with some basic info. Can you please send your kernel config 
and the output of 'dmesg' after a boot with a "slow" kernel?

Also, what distribution do you use (and what is its release/version)?

Cheers,
FJP

  reply	other threads:[~2009-09-25 22:51 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 [this message]
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

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=200909260051.34541.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=aneurin.price@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yinghai.lu@gmail.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.