kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>,
	"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	Arjan van de Ven <arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	"Pallipadi, Venkatesh" <venkate>
Cc: Alexey Fisher
	<bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Kernel Testers List
	<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Richard A. Holden III"
	<aciddeath-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Intel BIOS - Corrupted low memory at ffff880000004200
Date: Fri, 10 Jul 2009 13:52:38 +0200	[thread overview]
Message-ID: <20090710115238.GA8812@elte.hu> (raw)
In-Reply-To: <20090708113949.GA8960-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>


* Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> wrote:

> On Mon, Jul 06, 2009 at 06:24:47PM +0200, Alexey Fisher wrote:
> > Hallo Ingo, Richard.
> >
> > I'm getting "Corrupted low memory" trace with my Intel DG45ID 
> > board after resume. This board has different dmi-bios-vendor... 
> > so probably it will be nice to have it in your patch.
> 
> I'm beginning to think that we should be doing this on all 
> hardware, perhaps with a kernel option to disable it for embedded 
> devices that really need that 64K. The low-memory corruption issue 
> seems to be very widespread.

The problem is that the BIOS corrupted memory that it also marked as 
'usable' in its E820 map it gave to the kernel. If that memory is 
not usable, it should not have been marked as such. Also, some of 
the reports showed corruption beyond this range so the workaround is 
not universal.

So i'd really like to know what is happening there, instead of just 
zapping support for 64K of RAM on the majority of Linux systems.

We might end up doing the same thing in the end (i.e. disable that 
64k of RAM) - but it should be an informed decision, not a wild stab 
in the dark.

	Ingo

  parent reply	other threads:[~2009-07-10 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 14:56 Intel BIOS - Corrupted low memory at ffff880000004200 Alexey Fisher
2009-07-06 16:24 ` Alexey Fisher
     [not found]   ` <4A52254F.8080103-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-08 11:39     ` Matthew Garrett
     [not found]       ` <20090708113949.GA8960-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-07-09 23:19         ` Pavel Machek
2009-07-10 11:52         ` Ingo Molnar [this message]
     [not found]           ` <20090710115238.GA8812-X9Un+BFzKDI@public.gmane.org>
2009-07-10 12:16             ` Alexey Fisher
     [not found]               ` <4A573131.40601-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-10 13:05                 ` Thomas Gleixner
     [not found]                   ` <alpine.LFD.2.00.0907101504030.2768-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-07-10 14:04                     ` Alexey Fisher
2009-07-10 14:44                     ` Alexey Fisher
2009-07-10 14:59             ` H. Peter Anvin
     [not found]               ` <4A575735.9050208-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2009-07-11  9:41                 ` Alexey Fisher

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=20090710115238.GA8812@elte.hu \
    --to=mingo-x9un+bfzkdi@public.gmane.org \
    --cc=aciddeath-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
    --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).