From: Ethan Weinstein <lists@stinkfoot.org>
To: Magnus Damm <damm@opensource.se>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: CONFIG_HIGHMEM
Date: Thu, 20 Feb 2003 14:37:04 -0500 [thread overview]
Message-ID: <3E552E60.8040701@stinkfoot.org> (raw)
In-Reply-To: <20030220173252.43c77198.damm@opensource.se>
I had lots of issues with CONFIG_HIMEM+CONFIG_SMP with a dual G4-533
with 1.5G of RAM, until I started using 2.4.20-ben(x).
Ethan
Magnus Damm wrote:
>Hi,
>
>I recently bought more memory to my G4 Cube.
>The gentoo kernel ppc-sources-2.4.20-r2 gives
>me various oopses when I enable CONFIG_HIGHMEM.
>
>What kernel tree should I try? linuxppc_2_4?
>
>What do people run on their stable machines
>with more than 768Mbyte memory?
>
>thanks.
>
>/ magnus
>
>
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-20 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 17:32 CONFIG_HIGHMEM Magnus Damm
2003-02-20 19:35 ` CONFIG_HIGHMEM vinai
2003-02-20 19:37 ` Ethan Weinstein [this message]
2003-02-20 23:54 ` CONFIG_HIGHMEM Kain
2003-02-22 17:23 ` CONFIG_HIGHMEM Magnus Damm
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=3E552E60.8040701@stinkfoot.org \
--to=lists@stinkfoot.org \
--cc=damm@opensource.se \
--cc=linuxppc-dev@lists.linuxppc.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).