From: "H. Peter Anvin" <hpa@zytor.com>
To: Yuhong Bao <yuhongbao_386@hotmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, gregkh@suse.de
Subject: Re: Windows side agrees that lowmem corruption is a problem too
Date: Tue, 08 Jun 2010 12:06:05 -0700 [thread overview]
Message-ID: <4C0E949D.6090002@zytor.com> (raw)
In-Reply-To: <SNT125-W34B02C6BF1C272DC47AF7DC3D60@phx.gbl>
On 06/08/2010 11:28 AM, Yuhong Bao wrote:
>
> Adding mingo and gregkh to CC list.
>> Remember the lowmem corruption problems that lead the code that displays this to be added to Linux:> AMI BIOS detected: BIOS may corrupt low RAM, working around it.> which was IMO way too broad. Good news, the Windows side agree that this is a problem too:> http://www.microsoft.com/whdc/system/platform/firmware/mem-corrupt.mspx>> Yuhong Bao
>
Hardly "way too broad". I'm starting to think we should enable it
unconditionally, given the number of machines which have exhibited that
problem. As shown in the whitepaper, Vista/Win7 even avoid using
< 1 MB for a lot of things, presumably for this reason.
If it only was suspend, it would be one thing, but from what I've seen
it has been known to happen at other times too (e.g. HDMI cable insertion!)
-hpa
next prev parent reply other threads:[~2010-06-08 19:06 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 [this message]
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
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=4C0E949D.6090002@zytor.com \
--to=hpa@zytor.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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