* Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig
@ 2014-08-05 13:26 Arnab Basu
2014-08-05 13:40 ` Will Deacon
2014-08-05 14:08 ` Christopher Covington
0 siblings, 2 replies; 6+ messages in thread
From: Arnab Basu @ 2014-08-05 13:26 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig
2014-08-05 13:26 Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig Arnab Basu
@ 2014-08-05 13:40 ` Will Deacon
2014-08-05 18:46 ` Arnab Basu
2014-08-05 14:08 ` Christopher Covington
1 sibling, 1 reply; 6+ messages in thread
From: Will Deacon @ 2014-08-05 13:40 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Aug 05, 2014 at 02:26:42PM +0100, Arnab Basu wrote:
> Hi
Hi Arnab,
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig
2014-08-05 13:26 Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig Arnab Basu
2014-08-05 13:40 ` Will Deacon
@ 2014-08-05 14:08 ` Christopher Covington
2014-08-05 18:39 ` Arnab Basu
1 sibling, 1 reply; 6+ messages in thread
From: Christopher Covington @ 2014-08-05 14:08 UTC (permalink / raw)
To: linux-arm-kernel
On 08/05/2014 09:26 AM, Arnab Basu wrote:
> 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
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig
2014-08-05 14:08 ` Christopher Covington
@ 2014-08-05 18:39 ` Arnab Basu
2014-08-05 20:17 ` Christopher Covington
0 siblings, 1 reply; 6+ messages in thread
From: Arnab Basu @ 2014-08-05 18:39 UTC (permalink / raw)
To: linux-arm-kernel
On 08/05/2014 07:38 PM, Christopher Covington wrote:
> On 08/05/2014 09:26 AM, Arnab Basu wrote:
>> 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
> Christopher
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig
2014-08-05 13:40 ` Will Deacon
@ 2014-08-05 18:46 ` Arnab Basu
0 siblings, 0 replies; 6+ messages in thread
From: Arnab Basu @ 2014-08-05 18:46 UTC (permalink / raw)
To: linux-arm-kernel
On 08/05/2014 07:10 PM, Will Deacon wrote:
> On Tue, Aug 05, 2014 at 02:26:42PM +0100, Arnab Basu wrote:
>> Hi
>
> Hi Arnab,
>
>> 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).
>
Thanks for explaining Will.
Arnab
> Will
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig
2014-08-05 18:39 ` Arnab Basu
@ 2014-08-05 20:17 ` Christopher Covington
0 siblings, 0 replies; 6+ messages in thread
From: Christopher Covington @ 2014-08-05 20:17 UTC (permalink / raw)
To: linux-arm-kernel
On 08/05/2014 02:39 PM, Arnab Basu wrote:
> On 08/05/2014 07:38 PM, Christopher Covington wrote:
>> On 08/05/2014 09:26 AM, Arnab Basu wrote:
>>> 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
> 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)
>
> 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
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-08-05 20:17 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-05 13:26 Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig Arnab Basu
2014-08-05 13:40 ` Will Deacon
2014-08-05 18:46 ` Arnab Basu
2014-08-05 14:08 ` Christopher Covington
2014-08-05 18:39 ` Arnab Basu
2014-08-05 20:17 ` Christopher Covington
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.