From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jcwren@jcwren.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.0-test2 vs 2.2.12 -- Some observations
Date: 08 Aug 2003 13:16:30 +0100 [thread overview]
Message-ID: <1060344989.4933.27.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200308071323.44884.jcwren@jcwren.com>
On Iau, 2003-08-07 at 18:23, J.C. Wren wrote:
> For reasons unknown, whereas 2.2.12 picked up the values for how much memory
> we have stuffed into a fake BIOS block, 2.6.0-test2 does not (nor did
> 2.5.69). I have to set a mem=7744k into the boot params. Anything more, and
> I get kernel paging faults at startup. I'm unclear why this is, but since it
> can be worked around at the moment, I can let it lay.
2.5.x/2.6 (and 2.4) use E820 memory sizing before E801 and earlier
systems. Make sure your E820 tables are right I guess.
> I have not run hdparm on the drives, but e2fsck coming up on a dirty
> partition is amazingly slow on 2.6.0-test2. On a 32MB CF card with 25% usage
> (about 300 files), it takes less than 10 seconds under 2.2.12. On
> 2.6.0-test2, I'm seeing on the order of 40+ seconds. Long enough, in fact,
> that the watchdog that makes sure the system has booted into the application
> is timing out and punting the system.
You bluecat probably sets umask by default if its designed to keep
latency low. So hdparm -u1 /dev/hda first.
next prev parent reply other threads:[~2003-08-08 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 14:38 Linux 2.4.22-pre10-ac1 DRI doesn't work with Mitch
2003-08-07 11:44 ` Alan Cox
2003-08-07 13:27 ` Marcelo Tosatti
2003-08-07 14:26 ` Christoph Hellwig
2003-08-07 14:27 ` Alan Cox
2003-08-07 14:47 ` Marcelo Tosatti
2003-08-07 15:37 ` Christoph Hellwig
2003-08-07 17:23 ` Kernel 2.6.0-test2 vs 2.2.12 -- Some observations J.C. Wren
2003-08-07 17:34 ` Andrew Morton
2003-08-07 18:44 ` J.C. Wren
2003-08-08 12:16 ` Alan Cox [this message]
2003-08-07 19:23 ` Linux 2.4.22-pre10-ac1 DRI doesn't work with Erik Andersen
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=1060344989.4933.27.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jcwren@jcwren.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;
as well as URLs for NNTP newsgroup(s).