-------------------- Start of forwarded message --------------------
X-From-Line: pixel Wed Feb 21 23:11:07 2001
Return-Path: <[EMAIL PROTECTED]>
Received: from 216.71.116.162 [216.71.116.162]
by localhost with IMAP (fetchmail-5.6.0)
for pixel@localhost (single-drop); Wed, 21 Feb 2001 23:11:07 +0100 (CET)
Received: from localhost (jgarzik@localhost)
by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) with SMTP id QAA27262;
Wed, 21 Feb 2001 16:08:48 -0600
Date: Wed, 21 Feb 2001 16:08:46 -0600 (CST)
From: Jeff Garzik <[EMAIL PROTECTED]>
To: Pixel <[EMAIL PROTECTED]>
cc: MandrakeSoft Internal <[EMAIL PROTECTED]>
Subject: Re: ack! grub bug...
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Lines: 43
Xref: leia.mandrakesoft.com mail.mandrake:8147
On Wed, 21 Feb 2001, Pixel wrote:
> Jeff Garzik <[EMAIL PROTECTED]> writes:
> > Ok... Phillip and I just finished debugging a kernel problem that
> > wasn't a kernel problem. :)
> >
> > grub -always- passes the "mem=XXX" command line option to the kernel.
>
> it's always been that way...
It works around a kernel bug. That is wrong in and of itself.
A kernel bug fix belongs in the kernel, not in grub.
> > For kernel 2.4, this is -bad- and -wrong-.
>
> why?
It completely overrides the BIOS memory map with a standard memory map
containing two sections: one for memory before 640k, and one for memory
after 1MB.
Newer machines have several regions of reserved memory outside and
inside these regions. grub's actions are suicide on newer laptops,
and machines like servers with lots of memory. Laptops have special
sections of memory above 1MB which must be reserved... Ditto for
ACPI tables. Using mem=XXX completely eliminates any information
that the BIOS has provided to the OS.
The Dells here in the office, in fact, have a special region
of reserved address space that is dedicated to the Random Number
Generator (RNG) and other devices attached to the Intel Firmware Hub.
This hardware-special region is no longer reserved, when booting with
grub. That means the kernel might try to address it directly, if you
have enough memory: boom, crash!
Grub cannot do this on kernel 2.4, and probably should not do it on
kernel 2.2. I must check for kernel 2.2... I think the 2.2 bug is
fixed. Definitely not for 2.4. It makes the kernel unstable to do so.
Jeff
-------------------- End of forwarded message --------------------
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
