From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test8 and HIGMEM = segfaults and panics?
Date: Tue, 21 Oct 2003 11:53:37 -0400 [thread overview]
Message-ID: <20031021155337.GF2617@rdlg.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
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 backed out the HIGHMEM and left it at 1.5Gigs and it seems to be
running fine again.
I poked around the archives and couldn't find anything in particular
related to this. Anyone seen anything similar, known bug I've missed?
Robert
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-10-21 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 15:53 Robert L. Harris [this message]
2003-10-21 19:03 ` 2.6.0-test8 and HIGMEM = segfaults and panics? Zan Lynx
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=20031021155337.GF2617@rdlg.net \
--to=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