From: Peter Seiderer <Peter.Seiderer@ciselant.de>
To: linux-kernel@vger.kernel.org
Subject: [Patch][2.4] Oops if limit of memory via 'mem=123' failed.
Date: Wed, 28 May 2003 15:39:15 +0200 [thread overview]
Message-ID: <20030528133915.GA1578@zodiak> (raw)
Hello,
the following patch would have saved me some time in wondering about the
'mem=XXX' kernel-parameter (more specific that initrd failed if mem=XXX is
greater than the available physical memory size).
Please apply if you think it would be helpful to other.
Peter
--- linux-2.4.20/arch/i386/kernel/setup.c_orig 2003-05-28
12:57:39.000000000 +0200
+++ linux-2.4.20/arch/i386/kernel/setup.c 2003-05-28
13:07:21.000000000 +0200
@@ -433,6 +433,7 @@
}
}
}
+ printk(KERN_ERR "Ooops! Limit of memory to %016Lx failed!\n", size);
}
static void __init add_memory_region(unsigned long long start,
unsigned long long size, int type)
reply other threads:[~2003-05-28 14:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030528133915.GA1578@zodiak \
--to=peter.seiderer@ciselant.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®