From: "H. Peter Anvin" <hpa@zytor.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Yuhong Bao <yuhongbao_386@hotmail.com>,
linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: Windows side agrees that lowmem corruption is a problem too
Date: Tue, 08 Jun 2010 13:31:29 -0700 [thread overview]
Message-ID: <4C0EA8A1.4020801@zytor.com> (raw)
In-Reply-To: <201006082122.25089.linux@rainbow-software.org>
On 06/08/2010 12:22 PM, Ondrej Zary wrote:
>>
>> Yep, patterns of some silly OSD bitmap showed up in one of the corruption -
>> firmware displaying a 'you inserted a cable' kind of icon somewhere and
>> messing up the SMM code or so ...
>>
>> I agree that dis-using <1M by default is probably the sanest option.
>
> But please limit it to newer systems only (DMI present && year > 200?). There
> are many old machines running fine. Losing 1MB from 16MB is a bad thing.
>
Disusing 64K is something we can do unconditionally (especially since
we're only talking about 60K -- 15 pages -- of actually usable memory
anyway.)
Dropping all the low 0.6 MB (which is what it really is) is probably
unacceptable by default, but perhaps it makes sense to use it only for
ZONE_DMA or something.
-hpa
next prev parent reply other threads:[~2010-06-08 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 18:28 Windows side agrees that lowmem corruption is a problem too Yuhong Bao
2010-06-08 19:06 ` H. Peter Anvin
2010-06-08 19:08 ` Ingo Molnar
2010-06-08 19:22 ` Ondrej Zary
2010-06-08 19:31 ` Yuhong Bao
2010-06-08 20:31 ` H. Peter Anvin [this message]
2010-06-08 20:49 ` Yuhong Bao
2010-06-11 1:15 ` Robert Hancock
2010-06-08 21:56 ` Alan Cox
2010-06-08 21:57 ` H. Peter Anvin
2010-06-09 1:08 ` Yuhong Bao
-- strict thread matches above, loose matches on Subject: below --
2010-06-08 18:12 Yuhong Bao
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=4C0EA8A1.4020801@zytor.com \
--to=hpa@zytor.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=mingo@elte.hu \
--cc=yuhongbao_386@hotmail.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