lkml.org 
[lkml]   [2004]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Sony S170 + 1GB ram => Yenta: ISA IRQ mask 0x0000
Date
Linus,

> Anyway, the problem seems to be that you are doing something bad with the
> user-defined RAM map, for some reason that is not obvious at all. Your
> bootup clearly shows:

> which means that the BIOS marks the 0x000000003ff70000 - 0000000040000000
> region properly reserved, but you bave overridden this (incorrectly)
> with:

OK, we don't do anything explicit to set the RAM map. so we looked at
setup.c to see where that might get triggered, and it gets turned on by
"mem=". But we don't use mem=... (meanwhile someone runs cat
/proc/cmdline...)

Where did that mem=1048000K come from ? (not me)

well, it must be the boot loader, as the kernel didn't add that, and we
didn't ... looking at the GRUB source ... ARGH: we see in stage2/boot.c in
that big comment about boot proto 2.03 that grub is indeed adding kernel
command line options, (even to 2.4.24 and 2.6.8). How can this be? Their
code says it shouldn't, but it does.

This now works fine with GRUB's --no-mem-option added. Never in all this
time have I seen GRUB trigger this piece of code and write mem= in on its
own. Oh well.

-- Lincoln @ EmperorLinux http://www.EmperorLinux.com

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

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.045 / U:0.756 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site