From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Jesse Barnes" <jbarnes@virtuousgeek.org>
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
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
Date: Mon, 4 Jun 2007 08:48:37 -0700 [thread overview]
Message-ID: <2c0942db0706040848y1d1c2ce9p521c65117244edf1@mail.gmail.com> (raw)
In-Reply-To: <200706040840.21593.jbarnes@virtuousgeek.org>
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
next prev parent reply other threads:[~2007-06-04 15:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 18:14 Justin Piszcz
2007-06-01 19:10 ` Jesse Barnes
2007-06-01 19:17 ` Justin Piszcz
2007-06-01 19:19 ` Justin Piszcz
2007-06-01 19:21 ` Jesse Barnes
2007-06-01 21:14 ` Andi Kleen
2007-06-01 20:19 ` Justin Piszcz
2007-06-01 20:24 ` Andi Kleen
2007-06-01 20:26 ` Justin Piszcz
2007-06-01 21:07 ` Jesse Barnes
2007-06-01 21:19 ` Andi Kleen
2007-06-01 21:35 ` Jesse Barnes
2007-06-01 21:41 ` Jesse Barnes
2007-06-02 1:05 ` Venki Pallipadi
2007-06-02 1:15 ` Jesse Barnes
2007-06-02 8:43 ` Justin Piszcz
2007-06-02 9:22 ` Andi Kleen
2007-06-02 20:11 ` Justin Piszcz
2007-06-03 9:15 ` Matt Keenan
2007-06-04 15:40 ` Jesse Barnes
2007-06-04 15:48 ` Ray Lee [this message]
2007-06-04 15:49 ` Justin Piszcz
2007-06-04 16:01 ` Ray Lee
2007-06-04 15:54 ` Jesse Barnes
2007-06-04 18:24 ` Andi Kleen
2007-06-04 18:13 ` Eric W. Biederman
2007-06-04 18:22 ` Justin Piszcz
2007-06-04 19:08 ` Justin Piszcz
2007-06-04 19:17 ` Jesse Barnes
2007-06-04 19:18 ` Alan Cox
2007-06-04 21:01 ` Eric W. Biederman
2007-06-05 0:59 ` Yinghai Lu
2007-06-05 1:38 ` Eric W. Biederman
2007-06-05 9:46 ` Andi Kleen
2007-06-05 13:18 ` Justin Piszcz
2007-06-05 17:20 ` Jesse Barnes
2007-06-07 8:47 ` Andi Kleen
2007-06-04 19:23 ` Andi Kleen
2007-06-04 19:24 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? II Andi Kleen
2007-06-05 0:54 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? Yinghai Lu
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=2c0942db0706040848y1d1c2ce9p521c65117244edf1@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=andi@firstfloor.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tank.en.mate@gmail.com \
--cc=venkatesh.pallipadi@intel.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
all inboxes | Powered by JetHome®