From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jeff@AmeriCom.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux SMP kernel bug with > 512M ram
Date: 06 Sep 2002 18:07:08 +0100 [thread overview]
Message-ID: <1031332028.9945.74.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020906165516.17282.qmail@solo.americom.com>
On Fri, 2002-09-06 at 17:55, jeff@AmeriCom.com wrote:
> I've been having problems with a few of our servers and I can't seem to find this
> problem mentioned anywhere else. All of the dual processor machines will not operate
> with greater than 512 megs of ram with the newer SMP kernels (2.4.7-10enterprise #1
2.4.7 is hardly "new". Red Hat has issued errata kernels going up to
2.4.9.
> SMP). Two of the dual P3 1ghz machines crash after a few minutes, when the memory
> usage gets high enough, I presume. The errors they spit out vary, but its only when
> I go over 512megs of ram, and only on dual processor machines. I had a slightly
Chipset or memory hardware problems seem the most likely cause if the
errors seem random or weird
> different problem when I tried to set it up on a dual p2 266 machine, when I go over
> 512 megs there, the system takes an hour to boot up, and everything crawls from
Thats BIOS. Thats a well known BIOS problem where the BIOS doesnt
configure the mtrr registers properly. You can work around that one by
tweaking the settings by hand or probably by getting a newer BIOS
next prev parent reply other threads:[~2002-09-06 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 16:55 jeff
2002-09-06 17:06 ` Martin J. Bligh
2002-09-06 17:07 ` Alan Cox [this message]
2002-09-06 20:50 ` jeff
2002-09-06 20:47 ` David S. Miller
[not found] <005a01c255ec$89be7b40$d281f6cc@WEASEL>
[not found] ` <fa.hqf5vev.1u6g19e@ifi.uio.no>
[not found] ` <fa.hqeru5v.1v6u3h8@ifi.uio.no>
2002-09-06 21:49 ` jeff
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=1031332028.9945.74.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeff@AmeriCom.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
all inboxes | Powered by JetHome®