Skip to contentSkip to conversation

Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig

DISCUSSION Arnab Basu 3 participants 6 messages Aug 5, 2014

lore
Share & tools
lore

Arnab Basu

author
#0 lore raw

Hi

While trying to boot Linux with an initrd I found that CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE are not part of the arm64 defconfig. Is this because no one has got around to adding them or is this something that has been omitted on purpose?

Thanks
Arnab

#1 lore raw
Quoted 1 line · Arnab Basu

Hi

Hi Arnab,

Quoted 4 lines

While trying to boot Linux with an initrd I found that CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE are not part of the arm64 defconfig. Is this because no one has got around to adding them or is this something that has been omitted on purpose?

Do we really want CONFIG_BLK_DEV_RAM=y by default? The Kconfig text for the options says:

Most normal users won't need the RAM disk functionality, and can thus say N here.

so I'd be inclined to say we should leave things as they are. The current defconfig is largely driven by our testing efforts, but I've been enabling other options that could benefit many people without hindering others (e.g. DEVTMPFS_MOUNT).

Will

#3 lore raw
In reply to Arnab Basu
Quoted 6 lines · Arnab Basu

Hi

While trying to boot Linux with an initrd I found that CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE are not part of the arm64 defconfig. Is this because no one has got around to adding them or is this something that has been omitted on purpose?

I've been running initrds fine without this option. What requires it?

Christopher

Signature · 3 lines
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
author
#4 lore raw
Quoted 10 lines · Christopher Covington
Quoted 6 lines · Arnab Basu

Hi

While trying to boot Linux with an initrd I found that CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE are not part of the arm64 defconfig. Is this because no one has got around to adding them or is this something that has been omitted on purpose?

I've been running initrds fine without this option. What requires it?

Without these options I get:

VFS: Cannot open root device "ram0" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions:

Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
CPU: 7 PID: 1 Comm: swapper/0 Not tainted 3.16.0+ #1
Call trace:
[<ffffffc000088084>] dump_backtrace+0x0/0x12c
[<ffffffc0000881c0>] show_stack+0x10/0x1c
[<ffffffc0004a686c>] dump_stack+0x74/0xc4
[<ffffffc0004a37dc>] panic+0xe4/0x220
[<ffffffc000635ed8>] mount_block_root+0x1d4/0x278
[<ffffffc000636090>] mount_root+0x114/0x134
[<ffffffc0006361ec>] prepare_namespace+0x13c/0x188
[<ffffffc000635b2c>] kernel_init_freeable+0x1b8/0x1dc
[<ffffffc0004a0fc4>] kernel_init+0xc/0xd4

...

[<ffffffc000083da0>] el1_irq+0x60/0xd0
[<ffffffc0000e0680>] cpu_startup_entry+0xfc/0x14c
[<ffffffc00008e7f0>] secondary_start_kernel+0x118/0x128
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on 

unknown-blo
ck(0,0)

With these options I get:

RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing unused kernel memory: 220K (ffffffc000636000 - ffffffc00066d000)

My kernel command line is:

Kernel command line: console=ttyS1,115200 root=/dev/ram0 earlyprintk=uart8250-8bit,0x21c0600

Any pointers on what else could be causing this?

Thanks
Arnab

Quoted 2 lines

Christopher

author
#2 lore raw
In reply to Will Deacon
Quoted 13 lines · Will Deacon
Quoted 1 line · Arnab Basu

Hi

Hi Arnab,

Quoted 4 lines

While trying to boot Linux with an initrd I found that CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE are not part of the arm64 defconfig. Is this because no one has got around to adding them or is this something that has been omitted on purpose?

Do we really want CONFIG_BLK_DEV_RAM=y by default? The Kconfig text for the options says:

Quoted 8 lines

Most normal users won't need the RAM disk functionality, and can thus say N here.

so I'd be inclined to say we should leave things as they are. The current defconfig is largely driven by our testing efforts, but I've been enabling other options that could benefit many people without hindering others (e.g. DEVTMPFS_MOUNT).

Thanks for explaining Will.

Arnab

Quoted 2 lines

Will

#5 lore raw
In reply to Arnab Basu
Quoted 10 lines · Arnab Basu
Quoted 9 lines · Christopher Covington
Quoted 6 lines · Arnab Basu

Hi

While trying to boot Linux with an initrd I found that CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE are not part of the arm64 defconfig. Is this because no one has got around to adding them or is this something that has been omitted on purpose?

I've been running initrds fine without this option. What requires it?

Perhaps I should have said "initramfs"--I was going by the QEMU option I use to specify it.

https://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt

Quoted 10 lines

Without these options I get:

VFS: Cannot open root device "ram0" or unknown-block(0,0): error -6

With these options I get:

RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing unused kernel memory: 220K (ffffffc000636000 - ffffffc00066d000)

Quoted 6 lines

My kernel command line is:

Kernel command line: console=ttyS1,115200 root=/dev/ram0 earlyprintk=uart8250-8bit,0x21c0600

Any pointers on what else could be causing this?

With a (newc/SVR4 format) CPIO archive and not setting root= at all in the command line I see:

Unpacking initramfs...
Freeing initrd memory: 256384K (fffffe0008000000 - fffffe0017a60000)

Christopher

Signature · 3 lines
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.