Re: mem= causes oops — Linux Kernel

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: mem= causes oops
  - From: Jan Engelhardt <[email protected]>

References:
- BIOS causes (exposes?) modprobe (load_module) kernel oops
  - From: "John Z. Bohach" <[email protected]>
- mem= causes oops (was Re: BIOS causes (exposes?) modprobe (load_module) kernel oops)
  - From: "John Z. Bohach" <[email protected]>
- Re: mem= causes oops (was Re: BIOS causes (exposes?) modprobe (load_module) kernel oops)
  - From: "Randy.Dunlap" <[email protected]>
- Re: mem= causes oops (was Re: BIOS causes (exposes?) modprobe (load_module) kernel oops)
  - From: "John Z. Bohach" <[email protected]>
- Re: mem= causes oops
  - From: Jan Engelhardt <[email protected]>

Prev by Date: Re: + mqueue-comment-fix.patch added to -mm tree
Next by Date: Re: 2.6.16-mm1 grub oddness
Previous by thread: Re: mem= causes oops
Next by thread: Re: mem= causes oops
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]