From: "H. Peter Anvin" <hpa@zytor.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org
Subject: Re: Bisected 3.9 regression: Corrupted low memory (x86, mm: Move reserving low memory later in initialization)
Date: Wed, 21 May 2014 10:34:58 -0700 [thread overview]
Message-ID: <537CE3C2.8030601@zytor.com> (raw)
In-Reply-To: <CACna6rxb2+xBFRt-g7ttkSB++-WtVEMycC7G=wf1ircKPW12ZQ@mail.gmail.com>
On 05/21/2014 06:31 AM, Rafał Miłecki wrote:
> On 16 May 2014 07:29, Rafał Miłecki <zajec5@gmail.com> wrote:
>> Sorry for the late report, this bug appears on my old notebook I don't
>> commonly use. Anyway, I've noticed following problem when using
>> 3.15-rc1:
>>
>> Corrupted low memory at ffff88000000be98 (be98 phys) = b02a000400000000
>
> Ping?
>
It's not a regression, but rather a progression: the checker now does
what it claims to do, which is to check for low memory corruption.
However, the checker is also rather useless as anything other than a
diagnostic tool. It tells you that your BIOS is corrupting memory, and
the solution to that is to reserve the memory, which we already do.
All the checker tells us is that on your system, yes, we really do need
to reserve the memory.
-hpa
next prev parent reply other threads:[~2014-05-21 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 5:29 Bisected 3.9 regression: Corrupted low memory (x86, mm: Move reserving low memory later in initialization) Rafał Miłecki
2014-05-21 13:31 ` Rafał Miłecki
2014-05-21 17:34 ` H. Peter Anvin [this message]
2014-05-21 17:58 ` Rafał Miłecki
2014-05-21 18:03 ` H. Peter Anvin
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=537CE3C2.8030601@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zajec5@gmail.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.