From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Alex Villacís Lasso" <a_villacis@palosanto.com>,
linux-kernel@vger.kernel.org
Subject: Re: Use of memmap= to forcibly recover memory in 3GB-4GB range - is this safe?
Date: Thu, 17 Jan 2013 16:03:17 +0100 [thread overview]
Message-ID: <50F812B5.5050507@fold.natur.cuni.cz> (raw)
In-Reply-To: <CAE9FiQVOYk8GLhPU2z2AiTk6qFKcf0WTii+1ckbmyDY79436vg@mail.gmail.com>
Yinghai Lu wrote:
> On Wed, Jan 16, 2013 at 4:24 PM, Alex Villacís Lasso
> <a_villacis@palosanto.com> wrote:
>> El 16/01/13 02:11, Yinghai Lu escribió:
>>
>>> On Tue, Jan 15, 2013 at 5:47 PM, Alex Villacís Lasso
>>> <a_villacis@palosanto.com> wrote:
>>>>
>>>> [ 0.000000] e820: BIOS-provided physical RAM map:
>>>> [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff]
>>>> usable
>>>> [ 0.000000] BIOS-e820: [mem 0x000000000009f400-0x000000000009ffff]
>>>> reserved
>>>> [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff]
>>>> reserved
>>>> [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000cf58ffff]
>>>> usable
>>>> [ 0.000000] BIOS-e820: [mem 0x00000000cf590000-0x00000000cf5e2fff]
>>>> ACPI
>>>> NVS
>>>> [ 0.000000] BIOS-e820: [mem 0x00000000cf5e3000-0x00000000cf5effff]
>>>> ACPI
>>>> data
>>>> [ 0.000000] BIOS-e820: [mem 0x00000000cf5f0000-0x00000000cf5fffff]
>>>> reserved
>>>> [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff]
>>>> reserved
>>>> [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff]
>>>> reserved
>>>> [ 0.000000] NX (Execute Disable) protection: active
>>>
>>> ..
>>>>
>>>> [ 0.000000] original variable MTRRs
>>>> [ 0.000000] reg 0, base: 4GB, range: 512MB, type WB
>>>> [ 0.000000] reg 1, base: 4608MB, range: 256MB, type WB
>>>> [ 0.000000] reg 2, base: 0GB, range: 2GB, type WB
>>>> [ 0.000000] reg 3, base: 2GB, range: 1GB, type WB
>>>> [ 0.000000] reg 4, base: 3GB, range: 256MB, type WB
>>>> [ 0.000000] reg 5, base: 3319MB, range: 1MB, type UC
>>>> [ 0.000000] reg 6, base: 3320MB, range: 8MB, type UC
>>>> [ 0.000000] reg 7, base: 3318MB, range: 1MB, type UC
>>>> [ 0.000000] total RAM covered: 4086M
>>>
>>> Can you apply attached debug patch to see if the raw e820 is right from
>>> BIOS ?
>
>> Done. The output is attached. I see no difference between raw and sanitized
>> maps.
>
> yeah, it is BIOS problem.
>
> you may either live with memmap= or try to get one BIOS update.
Hi Yinghai,
wouldn't it be useful for other to include this patch into the kernel? It might help
someone else. Provided it is printed only when extra debug is enabled in the kernel
I don't think it hurts. Right?
Actually, if it could do the check for differences automatically and print a warning
it would be even better.
Martin
prev parent reply other threads:[~2013-01-17 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 1:47 Alex Villacís Lasso
2013-01-16 2:28 ` H. Peter Anvin
2013-01-16 7:02 ` Yinghai Lu
2013-01-16 2:29 ` Steven Rostedt
2013-01-16 7:11 ` Yinghai Lu
2013-01-17 0:24 ` Alex Villacís Lasso
2013-01-17 0:31 ` Yinghai Lu
2013-01-17 15:03 ` Martin Mokrejs [this message]
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=50F812B5.5050507@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=a_villacis@palosanto.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®