Return-Path: <linux-kernel-owner+w=401wt.eu-S1756914AbXFDPss@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756914AbXFDPss (ORCPT <rfc822;w@1wt.eu>);
	Mon, 4 Jun 2007 11:48:48 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751280AbXFDPsm
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 4 Jun 2007 11:48:42 -0400
Received: from ug-out-1314.google.com ([66.249.92.171]:13306 "EHLO
	ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751134AbXFDPsl (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 4 Jun 2007 11:48:41 -0400
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=pWR9s8xtnaAJhtHh9fQFNFYMIL/aKi8J7c6lbzFd4Jfnn34qu0AI1bJuHGlXN1e6uOuWNa9My+oh0nj12EhxEAgzviQycOlyX3HyXovf/W1gZQR1mE6Zq8NkHmXHwYIgbJRgrqjb5YqaTjkF97ejE93aMDrl1oMxcd6qa7eda0s=
Message-ID: <2c0942db0706040848y1d1c2ce9p521c65117244edf1@mail.gmail.com>
Date: Mon, 4 Jun 2007 08:48:37 -0700
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Jesse Barnes" <jbarnes@virtuousgeek.org>
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
Cc: "Matt Keenan" <tank.en.mate@gmail.com>,
       "Justin Piszcz" <jpiszcz@lucidpixels.com>,
       "Andi Kleen" <andi@firstfloor.org>,
       "Venki Pallipadi" <venkatesh.pallipadi@intel.com>,
       linux-kernel@vger.kernel.org
In-Reply-To: <200706040840.21593.jbarnes@virtuousgeek.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <Pine.LNX.4.64.0706011410130.3716@p34.internal.lan>
	 <Pine.LNX.4.64.0706021610210.19116@p34.internal.lan>
	 <4662869A.9030700@gmail.com>
	 <200706040840.21593.jbarnes@virtuousgeek.org>
X-Google-Sender-Auth: cf9629fbcf7c0b44
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2485
Lines: 54

On 6/4/07, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Sunday, June 3, 2007 2:15:06 Matt Keenan wrote:
> > Justin Piszcz wrote:
> > > On Sat, 2 Jun 2007, Andi Kleen wrote:
> > >>> I feel, having a silent/transparent workaround is not a good idea.
> > >>> With that
> > >>
> > >> If enough RAM is chopped off users will notice. They tend to complain
> > >> when they miss RAM.  I don't like panic very much because for many
> > >> users it will be a show stopper (even when they are not blessed
> > >> with "quiet" boots like some distributions do)
> > >>
> > >> The message in dmesg could be also emphasized a bit with a little
> > >> ASCII art (but no <blink> tag in there)
> > >>
> > >> The problem I'm more worried about is if the system will be really
> > >> stable --- could it be that the memory controller is still
> > >> misconfigured and cause other stability issues? (we've had such
> > >> cases in the past). Also I'm not sure we can handle the case of
> > >> the MTRR wrong not at the end of memory but at the hole sanely.
> > >>
> > >> -Andi
> > >
> > > So far I have been booting with mem=8832M and have run stress/loaded
> > > the memory subsystem pretty good; what other tests should I run?
> > >
> > > It'd be nice if we could pose some sort of solution/warning for the
> > > future so other people do not have to experience the same problems.
> > >
> > > What are the next steps?
> >
> > Wouldn't it be possible for the e820/MTRR set up code detect the problem
> > and suggest a mem=xxxx that would fix the problem (while also
> > complaining that the BIOS is broken)?
>
> Yes, that should be fairly easy, though as Andi points out, if there are holes
> in the MTRR setup, things get a little trickier (I had an earlier patch to
> deal with this, but ended up with too many early boot issues).
>
> Maybe what Venki suggested would be best:  just detect the condition and
> panic, with a string telling the user to use mem=xxx (we can figure that out)
> and/or upgrade their BIOS.

Ick. Systems that used to boot fine would then panic on a kernel
upgrade. That's rather rude for a condition that's merely an
optimization (using all memory), rather than one of correctness. A
panic seems entirely inappropriate.

Ray
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/