Re: "My" crash when reading partition table

Pavel Machek (pavel@suse.cz)
Thu, 14 Oct 1999 10:46:00 +0200


Hi!

> You will notice that the second region is 128k short of a full 63meg. (63 +
> 1 = 64). When you set the command line to 64M, the system tries to use some
> memory that the bios is not making available as regular memory. Crash is
> inevitable. This is why I have been unhappy with advice on the list to
> "Just set mem= to however much memory you have."

I did mem=63M, not mem=64M. I can retry with mem=61M (but I think it
crashed, too.)

> If you like, you could try mem=65408K. (64M - 128k) Another option would
> be to turn ACPI off & see how it goes.
>
> That NVS reserved memory is interesting. (That's the type 4 region at the
> end.) Since Linux does not currently recognize NVS memory (and if it did, I
> don't know how it would address that range), any operation looking like an
> ACPI sleep is likely too be a bad thing...

What is NVS? Non-volatile-storage?
Pavel

-- 
The best software in life is free (not shareware)!		Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+

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