From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: jzb@aexorsyst.com, linux-kernel@vger.kernel.org
Subject: Re: mem= causes oops
Date: Sun, 26 Mar 2006 09:41:21 -0800 [thread overview]
Message-ID: <20060326094121.9464762a.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0603251948360.29793@yvahk01.tjqt.qr>
On Sat, 25 Mar 2006 19:50:35 +0100 (MET) Jan Engelhardt wrote:
>
> >Subject: Re: mem= causes oops (was Re: BIOS causes (exposes?) modprobe
> > (load_module) kernel oops)
> >
>
> Hm, seeing this mail reminds me of something I seen on SPARC just a while
> ago. Maybe it's just something on my side. If I specify `mem=65536`, that
> is, with no size suffix like M or G, what does Linux make out of it? 65536
> KB or 64 KB?
65536 bytes. All of the suffixes [KMG] are optional.
---
~Randy
next prev parent reply other threads:[~2006-03-26 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 4:05 BIOS causes (exposes?) modprobe (load_module) kernel oops John Z. Bohach
2006-03-22 9:06 ` Arjan van de Ven
2006-03-23 3:48 ` John Z. Bohach
2006-03-23 5:26 ` John Z. Bohach
2006-03-23 5:42 ` Randy.Dunlap
2006-03-24 17:36 ` mem= causes oops (was Re: BIOS causes (exposes?) modprobe (load_module) kernel oops) John Z. Bohach
2006-03-25 0:32 ` Randy.Dunlap
2006-03-25 18:36 ` John Z. Bohach
2006-03-25 18:50 ` mem= causes oops Jan Engelhardt
2006-03-26 17:41 ` Randy.Dunlap [this message]
2006-03-26 18:40 ` Jan Engelhardt
2006-04-05 19:07 ` mem= causes oops (was Re: BIOS causes (exposes?) modprobe (load_module) kernel oops) Randy.Dunlap
2006-04-06 16:18 ` John Z. Bohach
2006-04-06 20:18 ` [PATCH] mpparse: prevent table index out-of-bounds Randy.Dunlap
2006-04-07 5:34 ` John Z. Bohach
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=20060326094121.9464762a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=jengelh@linux01.gwdg.de \
--cc=jzb@aexorsyst.com \
--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®