And another question, since the kernel is booting with initramfs support, is it normal that it tries to run /init instead of bin/init or sbin/init
To be more precise, it runs this: if (ramdisk_execute_command) { run_init_process(ramdisk_execute_command); <---this printk(KERN_WARNING "Failed to execute %s\n", ramdisk_execute_command); } instead of this: run_init_process("/sbin/init"); run_init_process("/etc/init"); run_init_process("/bin/init"); run_init_process("/bin/sh"); is it normal? Thanks! 2012/8/30 stl <st.lamber...@gmail.com> > Thanks Rahul for your very quick answer. > Glad to hear this. > So, when does the message "VFS: Mounted root" appear? > Maybe when using init ramdisk (initrd) support? > > > > > 2012/8/30 Rahul Bedarkar <rpal...@gmail.com> > >> yes root file system is mounted correctly. It is just it didn't find init. >> >> On Thu, Aug 30, 2012 at 8:10 PM, stl <st.lamber...@gmail.com> wrote: >> > Hello all, >> > if I try to boot Linux 2.6.37 by supplying a configuration file to the >> > kernel to create initramfs_data.cpio, >> > (without any compression), is it normal that the kernel doesn't print >> the >> > well known message: >> > >> > VFS: Mounted root (<type> filesystem) >> > >> > even if the boot reaches the point where it tries to run init >> executable? >> > Does it mean that my rootfs is not correctly mounted? >> > >> > Here is the kernel output printed during the boot: >> > >> > <5>[ 0.000000] Linux version 2.6.37+ (gcc version 4.6.3 20120816 >> (GCC) ) >> > #57 Thu Aug 30 12:00:00 CEST 2012 >> > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping off. >> > Total pages: 2032 >> > [ 0.000000] Kernel command line: >> > [ 0.000000] PID hash table entries: 32 (order: -5, 128 bytes) >> > [ 0.000000] Dentry cache hash table entries: 1024 (order: 0, 4096 >> bytes) >> > [ 0.000000] Inode-cache hash table entries: 1024 (order: 0, 4096 >> bytes) >> > [ 0.000000] Memory: 7656k/8196k available (1098k kernel code, 536k >> > reserved, 2096117k data, 12k init) >> > [ 0.000000] SLUB: Genslabs=15, HWalign=16, Order=0-3, MinObjects=0, >> > CPUs=1, Nodes=1 >> > [ 0.000000] NR_IRQS:64 >> > [ 0.000000] Timer start: timer interrupt every 10 ms >> > [ 0.000000] console [ttyS0] enabled >> > [42949372.980000] Calibrating delay loop... 0.00 BogoMIPS (lpj=0) >> > [42949373.180000] pid_max: default: 32768 minimum: 301 >> > [42949373.200000] Security Framework initialized >> > [42949373.210000] Mount-cache hash table entries: 512 >> > [42949373.260000] khelper used greatest stack depth: 7548 bytes left >> > [42949373.340000] kworker/u:0 used greatest stack depth: 7324 bytes left >> > [42949373.500000] bio: create slab <bio-0> at 0 >> > [42949373.630000] kworker/u:0 used greatest stack depth: 7260 bytes left >> > [42949374.630000] kworker/u:0 used greatest stack depth: 7180 bytes left >> > [42949375.250000] VFS: Disk quotas dquot_6.5.2 >> > [42949375.270000] Dquot-cache hash table entries: 1024 (order 0, 4096 >> bytes) >> > [42949375.390000] msgmni has been set to 16 >> > [42949375.420000] Block layer SCSI generic (bsg) driver version 0.4 >> loaded >> > (major 253) >> > [42949375.430000] io scheduler noop registered >> > [42949375.440000] io scheduler deadline registered >> > [42949375.460000] io scheduler cfq registered (default) >> > [42949375.490000] Architecture Specific Serial Driver >> > [42949375.500000] ttyS0 at MMIO 0x40001000 (irq = 5) is a arch_uart >> > [42949375.700000] loop: module loaded >> > [42949375.720000] mice: PS/2 mouse device common for all mice >> > [42949375.780000] ------------[ cut here ]------------ >> > [42949375.800000] WARNING: at fs/proc/generic.c:589 .LBE364+0x0/0x2() >> > [42949375.810000] proc_dir_entry '/proc/schedstat' already registered >> > [42949375.820000] Modules linked in: >> > [42949375.830000] ---[ end trace 31baa4bbf69a8bbc ]--- >> > [42949375.850000] Failed to execute /init >> > [42949375.870000] Kernel panic - not syncing: No init found. Try >> passing >> > init= option to kernel. See Linux Documentation/init.txt for guidance. >> > >> > In my opinion, it seems to be correct because the following message >> doesn't >> > appear: >> > >> > Warning: unable to open an initial console >> > >> > This means that the file /dev/console has been found, so that the >> rootfs has >> > been correctly mounted, isn't it? >> > >> > >> > Thanks in advance for your help! >> > >> > >> > _______________________________________________ >> > Kernelnewbies mailing list >> > Kernelnewbies@kernelnewbies.org >> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> > >> > >
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies