On Wed, 28 Jun 2006 08:15:06 -0400 Rodrigo Amestica wrote: > Hi, I'm having troubles when using the vmalloc kernel parameter. > > My grub config looks as shown below. If I set vmalloc to anything > bigger than 128M (the default) then the kernel will not boot and it > will log the following on the console: > > VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel Panic - not syncing: VFS Unable to mount root fs on > unknown-block(0,0) > > If I specify 128M or less then the kernel will boot just fine and > /proc/meminfo will show the effect in VmallocTotal. > > Any hint on what I'm crashing with? This is a known problem with GRUB: it tries to put initrd at the highest possible address in memory, and assumes the standard vmalloc area size. You need to trick GRUB into thinking that your machine has less memory by using "uppermem 524288" (512M) or even lower - then the initrd data will still be accessible for the kernel even with larger vmalloc area. http://lkml.org/lkml/2005/4/4/283 http://lists.linbit.com/pipermail/drbd-user/2005-April/002890.html > ps: my kernel version is 2.6.15.2, and my machine is a dual opteron > with 2GB of ram > > title with vmalloc > root (hd0,0) Add "uppermem 524288" here. > kernel /boot/vmlinuz ro root=LABEL=/ vmalloc=256M > initrd /boot/initrd.img
Attachment:
pgpKAkGdiIyI5.pgp
Description: PGP signature
- Follow-Ups:
- Re: vmalloc kernel parameter
- From: "H. Peter Anvin" <[email protected]>
- Re: vmalloc kernel parameter
- From: Rodrigo Amestica <[email protected]>
- Re: vmalloc kernel parameter
- References:
- vmalloc kernel parameter
- From: Rodrigo Amestica <[email protected]>
- vmalloc kernel parameter
- Prev by Date: Re: Kernel API Reference Documentation
- Next by Date: Re: [Suspend2][ 0/9] Extents support.
- Previous by thread: vmalloc kernel parameter
- Next by thread: Re: vmalloc kernel parameter
- Index(es):
 |