From: Tom Vier <tmv@comcast.net>
To: linux-kernel@vger.kernel.org
Cc: "Richard B. Johnson" <root@chaos.analogic.com>
Subject: Re: Dual Opteron 248s w/ 8GB RAM on Tyan K8W (S2885)
Date: Sun, 2 May 2004 21:45:03 -0400 [thread overview]
Message-ID: <20040503014503.GA2337@zero> (raw)
In-Reply-To: <Pine.LNX.4.53.0404300657420.3289@chaos>
On Fri, Apr 30, 2004 at 07:01:38AM -0400, Richard B. Johnson wrote:
> It can't be. The only CPU(s) that would know anything about it and
> thus be able to use that RAM are running the operating system.
unless it's reserving it for cross-boot data. i remember there being some
error (ecc, machine checks?) logging option in the bios setup. *shrug* i
don't know much about x86(-64) bios. openboot and srm do save state, since
you can drop back to them without rebooting.
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
next prev parent reply other threads:[~2004-05-03 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 22:53 Dual Opteron 248s w/ 8GB RAM on Tyan K8W (S2885) Bryan Stillwell
[not found] ` <200404300005.02814.vda@port.imtp.ilyichevsk.odessa.ua>
2004-04-29 21:17 ` Bryan Stillwell
2004-04-30 2:15 ` Tom Vier
2004-04-30 5:00 ` Bryan Stillwell
2004-04-30 11:01 ` Richard B. Johnson
2004-05-03 1:45 ` Tom Vier [this message]
[not found] <E45C36E01BB62E4ABE34C82372A928E0020A32@iron.Vnet.com>
2004-05-03 18:23 ` Bryan Stillwell
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=20040503014503.GA2337@zero \
--to=tmv@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox