From: Zan Lynx <zlynx@acm.org>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test8 and HIGMEM = segfaults and panics?
Date: 21 Oct 2003 13:03:02 -0600 [thread overview]
Message-ID: <1066762982.5055.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20031021155337.GF2617@rdlg.net>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Tue, 2003-10-21 at 09:53, Robert L. Harris wrote:
> I'm running a dual-athalon system. When I compiled the 2.6.0-test8 kernel I
> enabled HIGHMEM for 4 Gigs as I'm at 1.5G now and planning on purchasing
> an additional 512Meg DIMM next weekend (yeah, should have with the
> 1.5Gig).
>
> At any rate the box comes up just fine and runs for a while but once the
> memory is in use for a few hours and seems to exceed 220+ Megs about any
> command I execute will Segfault and the kernel has panic'd twice
> (couldn't read the whole oops).
I run a dual athlon system with 2 GB, and it has never done anything
like that.
Have you run memtest86 on your system to verify it isn't a physical
memory problem?
Are you using registered RAM chips? I seem to remember from my
motherboard documentation that registered is required to use more than 2
memory slots.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-21 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 15:53 2.6.0-test8 and HIGMEM = segfaults and panics? Robert L. Harris
2003-10-21 19:03 ` Zan Lynx [this message]
2003-10-21 19:58 ` Robert L. Harris
2003-10-21 21:26 ` Zan Lynx
2003-10-21 22:39 ` Robert L. Harris
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=1066762982.5055.3.camel@localhost.localdomain \
--to=zlynx@acm.org \
--cc=Robert.L.Harris@rdlg.net \
--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