From: "Lincoln D. Durey" <durey@EmperorLinux.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Hinds <dhinds@sonic.net>,
Emperor Research <research@EmperorLinux.com>
Subject: Re: Sony S170 + 1GB ram => Yenta: ISA IRQ mask 0x0000
Date: Tue, 26 Oct 2004 19:18:23 -0400 [thread overview]
Message-ID: <200410261918.23502.durey@EmperorLinux.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410261117530.28839@ppc970.osdl.org>
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
next prev parent reply other threads:[~2004-10-26 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 17:42 Sony S170 + 1GB ram => Yenta: ISA IRQ mask 0x0000 Lincoln D. Durey
2004-10-26 18:28 ` Linus Torvalds
2004-10-26 21:58 ` David Hinds
2004-10-26 23:18 ` Lincoln D. Durey [this message]
2004-10-26 23:44 ` Linus Torvalds
2004-10-27 0:08 ` William Lee Irwin III
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=200410261918.23502.durey@EmperorLinux.com \
--to=durey@emperorlinux.com \
--cc=dhinds@sonic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=research@EmperorLinux.com \
--cc=torvalds@osdl.org \
/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