mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Cc: "Jesse Barnes" <jbarnes@virtuousgeek.org>,
	"Matt Keenan" <tank.en.mate@gmail.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 09:01:06 -0700	[thread overview]
Message-ID: <2c0942db0706040901n473afb20x800cb489e3f7732b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706041149160.18306@p34.internal.lan>

On 6/4/07, Justin Piszcz <jpiszcz@lucidpixels.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

  reply	other threads:[~2007-06-04 16:01 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
2007-06-04 15:49                       ` Justin Piszcz
2007-06-04 16:01                         ` Ray Lee [this message]
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=2c0942db0706040901n473afb20x800cb489e3f7732b@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®