From: "Johan Ekenberg" <johan@ekenberg.se>
To: "\"Brad Dameron\"" <bdameron@tscnet.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Lockups with 2.4.14 and 2.4.16
Date: Wed, 12 Dec 2001 01:38:07 +0100 [thread overview]
Message-ID: <000b01c182a5$44bd35b0$050010ac@FUTURE> (raw)
> We use the same motherboards. And for some reason if you put 1 gig in them
> exactly and then in the kernel under "Processor type/High Memory Support"
we
> set it to use 4 gig it locks up the machine every once in a while.
How would it lock up? Could you describe the symptoms in more detail so that
I can compare?
> We ended up putting in 1.5 gig of ram and that seemed to fix it.
Oh, how did you do that? We tried to put 2Gb on one board but it wouldn't
recognize more than 1 Gb. I'm fairly sure we flashed the bios with the
latest firmware. Which board is it you have, Epox BXB-S or Epox KP6-BS?
> If you didn't
> compile in the 4 gig support Linux wouldn't recognize the full 1 gig of
> memory for some reason. This is on a Redhat 7.1 machine with 2.4.x
kernel's.
Yes, I noticed that too. Unfortunately, I've tested with both 1G and 4G
support when configuring the kernel, and the i/o lockups still happen.
next reply other threads:[~2001-12-12 0:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 0:38 Johan Ekenberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 23:56 SV: Lockups with 2.4.14 and 2.4.16 Johan Ekenberg
2001-12-14 16:49 ` Chris Mason
2001-12-14 17:26 ` Andrew Morton
2001-12-14 17:53 ` Chris Mason
2001-12-14 18:32 ` Andrea Arcangeli
2001-12-14 18:55 ` Chris Mason
2001-12-14 18:57 ` Andrew Morton
2001-12-14 19:16 ` Andrea Arcangeli
2001-12-20 13:29 ` Chris Mason
2001-12-14 19:26 ` Jan Kara
2001-12-14 19:21 ` Jan Kara
2001-12-11 23:29 Johan Ekenberg
2001-12-11 23:47 ` Alan Cox
2001-12-12 0:12 ` Brad Dameron
2001-12-12 0:47 ` Chris Mason
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='000b01c182a5$44bd35b0$050010ac@FUTURE' \
--to=johan@ekenberg.se \
--cc=bdameron@tscnet.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