From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: madduck@madduck.net
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Disabling physical RAM regions for testing
Date: Tue, 05 Aug 2014 08:26:01 -0400 [thread overview]
Message-ID: <53E0CD59.10003@gmail.com> (raw)
In-Reply-To: <20140805114010.GA14521@fishbowl.rw.madduck.net>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
On 2014-08-05 07:40, martin f krafft wrote:
> Hello,
>
> A NAS seems to be having RAM problems, leading me to want to swap
> out DIMMs until I found the offender; I'd rather not go to the rack
> every time I need to make a change.
>
> Is there a way to declare a DIMM unavailable to Linux with a boot
> parameter? There is mem= and memmap= but i cannot figure them out.
>
> I have two 4Gb DIMMs in there and I just want to disable one, then
> the other…
>
> This is the e820 physical RAM map:
>
> [ 0.000000] e820: BIOS-provided physical RAM map:
> [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
> [ 0.000000] BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bff8ffff] usable
> [ 0.000000] BIOS-e820: [mem 0x00000000bff9e000-0x00000000bff9ffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000bffa0000-0x00000000bffaa5ff] ACPI data
> [ 0.000000] BIOS-e820: [mem 0x00000000bffaa600-0x00000000bffdffff] ACPI NVS
> [ 0.000000] BIOS-e820: [mem 0x00000000bffe0000-0x00000000bfffffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000022fffffff] usable
>
> But what do I do with those info?
>
The e820 is probably not what you want to be looking at. I would
suggest looking into memory hot-plug/hot-remove support, IIRC the
hot-remove support allows you to bring a bank offline.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2014-08-05 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 11:40 Disabling physical RAM regions for testing martin f krafft
2014-08-05 12:26 ` Austin S Hemmelgarn [this message]
2014-08-05 13:06 ` martin f. krafft
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=53E0CD59.10003@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madduck@madduck.net \
/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