[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c0942db0706040901n473afb20x800cb489e3f7732b@mail.gmail.com>
Date: Mon, 4 Jun 2007 09:01:06 -0700
From: "Ray Lee" <ray-lk@...rabbit.org>
To: "Justin Piszcz" <jpiszcz@...idpixels.com>
Cc: "Jesse Barnes" <jbarnes@...tuousgeek.org>,
"Matt Keenan" <tank.en.mate@...il.com>,
"Andi Kleen" <andi@...stfloor.org>,
"Venki Pallipadi" <venkatesh.pallipadi@...el.com>,
linux-kernel@...r.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?
On 6/4/07, Justin Piszcz <jpiszcz@...idpixels.com> wrote:
> On Mon, 4 Jun 2007, Ray Lee wrote:
> > 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.
>
> While I am unsure of the 'best' solution, if they boot and it does not
> panic but takes 10 minutes to boot, people are going to seriously wonder
> what is going on?
<goes and re-reads thread more carefully> Oh, hmm.
I think a big fat warning with asterisks in the bootup is a good
thing, but panicking when there's no need is never a good idea. If the
system takes that long to boot up, I'm certain the first thing they'll
do is to type dmesg | less to look for anomalies.
Ray
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists