From: Tarkan Erimer <tarkan@netone.net.tr>
To: alex-lists-linux-kernel@yuriev.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Visible boot slowdown between 2.6.24.3 and 2.6.22.2
Date: Wed, 26 Mar 2008 10:05:28 +0200 [thread overview]
Message-ID: <47EA03C8.8030806@netone.net.tr> (raw)
In-Reply-To: <20080326024829.GA20476@s1.yuriev.com>
alex-lists-linux-kernel@yuriev.com wrote:
> Hi,
> I saw a significant slowdown of a bootup time after 2.6.22.2 was
> upgraded to 2.6.24.3. Visibly I can see the issue when the boot process gets
> to running udev - now it sits for good minute or two. I can also visibly see
> a slowdown when I do "ps aux" under the new kernel vs. old one.
>
> This is a relatively old system - 500 Mhz P3 Celeron with 512M RAM.
>
> Any debugging suggestions are appreciated...
>
It's the same for me,too. I tried 2.6.24.3 on my IBM R40, which has 1.4
GHZ CPU, the boot process is very slow. I didn't run "ps aux". But, I'll
try that out and let know.
next prev parent reply other threads:[~2008-03-26 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 2:48 Visible boot slowdown between 2.6.24.3 and 2.6.22.2 alex-lists-linux-kernel
2008-03-26 6:43 ` Andrew Morton
2008-03-26 8:05 ` Tarkan Erimer [this message]
2008-03-26 16:25 ` Jan Engelhardt
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=47EA03C8.8030806@netone.net.tr \
--to=tarkan@netone.net.tr \
--cc=alex-lists-linux-kernel@yuriev.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