From: benh@kernel.crashing.org
To: Christopher Murtagh <christopher.murtagh@mcgill.ca>
Cc: <yellowdog-devel@lists.yellowdoglinux.com>,
Eric Leblond <eric@regit.org>, <linuxppc-dev@lists.linuxppc.org>,
"Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Subject: Re: Support for new Dual G4 1 Gig machines?
Date: Tue, 29 Jan 2002 13:39:55 +0100 [thread overview]
Message-ID: <20020129123955.29280@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201281521410.9879-100000@blues.wcg.mcgill.ca>
> .../...
>
> All of the above machines are running 2.4.18pre1 running Apache 1.3.20,
>PHP 4.1.1, Postgres 7.1.3, htdig 3.1.16. Both the 500 and the 800 have 1GB
>of RAM, but the 450 only has 512, so perhaps it is a high-memory with
>networking problem?
>
> So, SMP on the PPC platform has some work needed I'm afraid. I'd be happy
>to help in any testing if someone wants me to, as I'd love to actually use
>that other CPU on my dual 800. :-)
I recently spotted a problem with >512Mb (CONFIG_HIGHMEM or not) & SMP that
is fixed in the current bk _2_4 (2.4.18pre7). I also sent a fix to Marcelo
that should hopefully be in the next 2.4.18preX release.
You should also use sungem preferably to the old gmac driver.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-29 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C55A9A8.9B3EB57E@wvi.com>
2002-01-28 20:34 ` Support for new Dual G4 1 Gig machines? Christopher Murtagh
2002-01-29 12:39 ` benh [this message]
2002-01-29 14:52 ` Christopher Murtagh
2002-01-29 15:01 ` Holger Bettag
2002-01-29 17:01 ` Edward Swarthout
2002-01-29 19:09 ` benh
2002-01-29 19:08 ` benh
2002-01-30 9:44 ` Alain RICHARD
2002-01-30 14:55 ` benh
2002-01-29 17:25 ` Derrik Pates
2002-01-29 22:06 ` Tom Rini
2002-01-30 7:00 ` Eric Leblond
2002-01-28 19:40 Kevin B. Hendricks
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=20020129123955.29280@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=christopher.murtagh@mcgill.ca \
--cc=eric@regit.org \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yellowdog-devel@lists.yellowdoglinux.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.