Re: Is my rootfs correctly mounted?
On Thu, Aug 30, 2012 at 8:38 PM, stl wrote:
> 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?
>
yes it is obvious from code (init/main.c) that it tries /init
/sbin/init unless it fails to execute anything.
> Thanks!
>
>
> 2012/8/30 stl
>>
>> 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?
I don't know but if it fails to mount root file system or file system
is just a garbage with initramfs the well known log is "kernel panic:
junk in compressed archive"
>>
>>
>>
>>
>> 2012/8/30 Rahul Bedarkar
>>>
>>> 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 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 ( 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.00] Linux version 2.6.37+ (gcc version 4.6.3 20120816
>>> > (GCC) )
>>> > #57 Thu Aug 30 12:00:00 CEST 2012
>>> > [0.00] Built 1 zonelists in Zone order, mobility grouping off.
>>> > Total pages: 2032
>>> > [0.00] Kernel command line:
>>> > [0.00] PID hash table entries: 32 (order: -5, 128 bytes)
>>> > [0.00] Dentry cache hash table entries: 1024 (order: 0, 4096
>>> > bytes)
>>> > [0.00] Inode-cache hash table entries: 1024 (order: 0, 4096
>>> > bytes)
>>> > [0.00] Memory: 7656k/8196k available (1098k kernel code, 536k
>>> > reserved, 2096117k data, 12k init)
>>> > [0.00] SLUB: Genslabs=15, HWalign=16, Order=0-3, MinObjects=0,
>>> > CPUs=1, Nodes=1
>>> > [0.00] NR_IRQS:64
>>> > [0.00] Timer start: timer interrupt every 10 ms
>>> > [0.00] console [ttyS0] enabled
>>> > [42949372.98] Calibrating delay loop... 0.00 BogoMIPS (lpj=0)
>>> > [42949373.18] pid_max: default: 32768 minimum: 301
>>> > [42949373.20] Security Framework initialized
>>> > [42949373.21] Mount-cache hash table entries: 512
>>> > [42949373.26] khelper used greatest stack depth: 7548 bytes left
>>> > [42949373.34] kworker/u:0 used greatest stack depth: 7324 bytes
>>> > left
>>> > [42949373.50] bio: create slab at 0
>>> > [42949373.63] kworker/u:0 used greatest stack depth: 7260 bytes
>>> > left
>>> > [42949374.63] kworker/u:0 used greatest stack depth: 7180 bytes
>>> > left
>>> > [42949375.25] VFS: Disk quotas dquot_6.5.2
>>> > [42949375.27] Dquot-cache hash table entries: 1024 (order 0, 4096
>>> > bytes)
>>> > [42949375.39] msgmni has been set to 16
>>> > [42949375.42] Block layer SCSI generic (bsg) driver version 0.4
>>> > loaded
>>> > (major 253)
>>> > [42949375.43] io scheduler noop registered
>>> > [42949375.44] io scheduler deadline registered
>>> > [42949375.46] io scheduler cfq registered (default)
>>> > [42949375.49] Architecture Specific Serial Driver
>>> > [42949375.50] ttyS0 at MMIO 0x40001000 (irq = 5) is a arch_uart
>>> > [42949375.70] loop: module loaded
>>> > [42949375.72] mice: PS/2 mouse device common for all mice
>>> > [42949375.78] [ cut here ]
>>> > [42949375.80] WARNING: at fs/proc/generic.c:589 .LBE364+0x0/0x2()
>>> > [42949375.81] proc_dir_entry '/proc/schedstat' already registered
>>> > [42949375.82] Modules linked in:
>>> > [42949375.83] ---[ end trace 31baa4bbf69a8bbc ]---
>>> > [42949375.85] Failed to execute /init
>>> > [42949375.87] 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!
>>> >
>>> >
>>> > ___
>>> > Kernel
Re: Issue with ps -l command "Unknown HZ value! (744514) Assume 100."
Hi... please, don't top post... On Thu, Aug 30, 2012 at 6:51 PM, KARTHIK SEKURU wrote: > > If yes,then would replacing the linux-3.4.tar.bz2 with the one > modified(having CONFIG_HZ as 25) by me would make the userspace take 25HZ as > default.Am i correct? can't guarantee that, but I think it's worth to try -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Is my rootfs correctly mounted?
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
> 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
>
>> 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 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 ( 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.00] Linux version 2.6.37+ (gcc version 4.6.3 20120816
>> (GCC) )
>> > #57 Thu Aug 30 12:00:00 CEST 2012
>> > [0.00] Built 1 zonelists in Zone order, mobility grouping off.
>> > Total pages: 2032
>> > [0.00] Kernel command line:
>> > [0.00] PID hash table entries: 32 (order: -5, 128 bytes)
>> > [0.00] Dentry cache hash table entries: 1024 (order: 0, 4096
>> bytes)
>> > [0.00] Inode-cache hash table entries: 1024 (order: 0, 4096
>> bytes)
>> > [0.00] Memory: 7656k/8196k available (1098k kernel code, 536k
>> > reserved, 2096117k data, 12k init)
>> > [0.00] SLUB: Genslabs=15, HWalign=16, Order=0-3, MinObjects=0,
>> > CPUs=1, Nodes=1
>> > [0.00] NR_IRQS:64
>> > [0.00] Timer start: timer interrupt every 10 ms
>> > [0.00] console [ttyS0] enabled
>> > [42949372.98] Calibrating delay loop... 0.00 BogoMIPS (lpj=0)
>> > [42949373.18] pid_max: default: 32768 minimum: 301
>> > [42949373.20] Security Framework initialized
>> > [42949373.21] Mount-cache hash table entries: 512
>> > [42949373.26] khelper used greatest stack depth: 7548 bytes left
>> > [42949373.34] kworker/u:0 used greatest stack depth: 7324 bytes left
>> > [42949373.50] bio: create slab at 0
>> > [42949373.63] kworker/u:0 used greatest stack depth: 7260 bytes left
>> > [42949374.63] kworker/u:0 used greatest stack depth: 7180 bytes left
>> > [42949375.25] VFS: Disk quotas dquot_6.5.2
>> > [42949375.27] Dquot-cache hash table entries: 1024 (order 0, 4096
>> bytes)
>> > [42949375.39] msgmni has been set to 16
>> > [42949375.42] Block layer SCSI generic (bsg) driver version 0.4
>> loaded
>> > (major 253)
>> > [42949375.43] io scheduler noop registered
>> > [42949375.44] io scheduler deadline registered
>> > [42949375.46] io scheduler cfq registered (default)
>> > [42949375.49] Architecture Specific Serial Driver
>> > [42949375.50] ttyS0 at MMIO 0x40001000 (irq = 5) is a arch_uart
>> > [42949375.70] loop: module loaded
>> > [42949375.72] mice: PS/2 mouse device common for all mice
>> > [42949375.78] [ cut here ]
>> > [42949375.80] WARNING: at fs/proc/generic.c:589 .LBE364+0x0/0x2()
>> > [42949375.81] proc_dir_entry '/proc/schedstat' already registered
>> > [42949375.82] Modules linked in:
>> > [42949375.83] ---[ end trace 31baa4bbf69a8bbc ]---
>> > [42949375.85] Failed to execute /init
>> > [42949375.87] 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
Re: Is my rootfs correctly mounted?
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 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 ( 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.00] Linux version 2.6.37+ (gcc version 4.6.3 20120816 (GCC) ) > #57 Thu Aug 30 12:00:00 CEST 2012 > [0.00] Built 1 zonelists in Zone order, mobility grouping off. > Total pages: 2032 > [0.00] Kernel command line: > [0.00] PID hash table entries: 32 (order: -5, 128 bytes) > [0.00] Dentry cache hash table entries: 1024 (order: 0, 4096 bytes) > [0.00] Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) > [0.00] Memory: 7656k/8196k available (1098k kernel code, 536k > reserved, 2096117k data, 12k init) > [0.00] SLUB: Genslabs=15, HWalign=16, Order=0-3, MinObjects=0, > CPUs=1, Nodes=1 > [0.00] NR_IRQS:64 > [0.00] Timer start: timer interrupt every 10 ms > [0.00] console [ttyS0] enabled > [42949372.98] Calibrating delay loop... 0.00 BogoMIPS (lpj=0) > [42949373.18] pid_max: default: 32768 minimum: 301 > [42949373.20] Security Framework initialized > [42949373.21] Mount-cache hash table entries: 512 > [42949373.26] khelper used greatest stack depth: 7548 bytes left > [42949373.34] kworker/u:0 used greatest stack depth: 7324 bytes left > [42949373.50] bio: create slab at 0 > [42949373.63] kworker/u:0 used greatest stack depth: 7260 bytes left > [42949374.63] kworker/u:0 used greatest stack depth: 7180 bytes left > [42949375.25] VFS: Disk quotas dquot_6.5.2 > [42949375.27] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > [42949375.39] msgmni has been set to 16 > [42949375.42] Block layer SCSI generic (bsg) driver version 0.4 loaded > (major 253) > [42949375.43] io scheduler noop registered > [42949375.44] io scheduler deadline registered > [42949375.46] io scheduler cfq registered (default) > [42949375.49] Architecture Specific Serial Driver > [42949375.50] ttyS0 at MMIO 0x40001000 (irq = 5) is a arch_uart > [42949375.70] loop: module loaded > [42949375.72] mice: PS/2 mouse device common for all mice > [42949375.78] [ cut here ] > [42949375.80] WARNING: at fs/proc/generic.c:589 .LBE364+0x0/0x2() > [42949375.81] proc_dir_entry '/proc/schedstat' already registered > [42949375.82] Modules linked in: > [42949375.83] ---[ end trace 31baa4bbf69a8bbc ]--- > [42949375.85] Failed to execute /init > [42949375.87] 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
Re: Is my rootfs correctly mounted?
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 > 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 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 ( 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.00] Linux version 2.6.37+ (gcc version 4.6.3 20120816 > (GCC) ) > > #57 Thu Aug 30 12:00:00 CEST 2012 > > [0.00] Built 1 zonelists in Zone order, mobility grouping off. > > Total pages: 2032 > > [0.00] Kernel command line: > > [0.00] PID hash table entries: 32 (order: -5, 128 bytes) > > [0.00] Dentry cache hash table entries: 1024 (order: 0, 4096 > bytes) > > [0.00] Inode-cache hash table entries: 1024 (order: 0, 4096 > bytes) > > [0.00] Memory: 7656k/8196k available (1098k kernel code, 536k > > reserved, 2096117k data, 12k init) > > [0.00] SLUB: Genslabs=15, HWalign=16, Order=0-3, MinObjects=0, > > CPUs=1, Nodes=1 > > [0.00] NR_IRQS:64 > > [0.00] Timer start: timer interrupt every 10 ms > > [0.00] console [ttyS0] enabled > > [42949372.98] Calibrating delay loop... 0.00 BogoMIPS (lpj=0) > > [42949373.18] pid_max: default: 32768 minimum: 301 > > [42949373.20] Security Framework initialized > > [42949373.21] Mount-cache hash table entries: 512 > > [42949373.26] khelper used greatest stack depth: 7548 bytes left > > [42949373.34] kworker/u:0 used greatest stack depth: 7324 bytes left > > [42949373.50] bio: create slab at 0 > > [42949373.63] kworker/u:0 used greatest stack depth: 7260 bytes left > > [42949374.63] kworker/u:0 used greatest stack depth: 7180 bytes left > > [42949375.25] VFS: Disk quotas dquot_6.5.2 > > [42949375.27] Dquot-cache hash table entries: 1024 (order 0, 4096 > bytes) > > [42949375.39] msgmni has been set to 16 > > [42949375.42] Block layer SCSI generic (bsg) driver version 0.4 > loaded > > (major 253) > > [42949375.43] io scheduler noop registered > > [42949375.44] io scheduler deadline registered > > [42949375.46] io scheduler cfq registered (default) > > [42949375.49] Architecture Specific Serial Driver > > [42949375.50] ttyS0 at MMIO 0x40001000 (irq = 5) is a arch_uart > > [42949375.70] loop: module loaded > > [42949375.72] mice: PS/2 mouse device common for all mice > > [42949375.78] [ cut here ] > > [42949375.80] WARNING: at fs/proc/generic.c:589 .LBE364+0x0/0x2() > > [42949375.81] proc_dir_entry '/proc/schedstat' already registered > > [42949375.82] Modules linked in: > > [42949375.83] ---[ end trace 31baa4bbf69a8bbc ]--- > > [42949375.85] Failed to execute /init > > [42949375.87] 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
Is my rootfs correctly mounted?
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 ( 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.00] Linux version 2.6.37+ (gcc version 4.6.3 20120816 (GCC) ) #57 Thu Aug 30 12:00:00 CEST 2012 [0.00] Built 1 zonelists in Zone order, mobility grouping off. Total pages: 2032 [0.00] Kernel command line: [0.00] PID hash table entries: 32 (order: -5, 128 bytes) [0.00] Dentry cache hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Memory: 7656k/8196k available (1098k kernel code, 536k reserved, 2096117k data, 12k init) [0.00] SLUB: Genslabs=15, HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] NR_IRQS:64 [0.00] Timer start: timer interrupt every 10 ms [0.00] console [ttyS0] enabled [42949372.98] Calibrating delay loop... 0.00 BogoMIPS (lpj=0) [42949373.18] pid_max: default: 32768 minimum: 301 [42949373.20] Security Framework initialized [42949373.21] Mount-cache hash table entries: 512 [42949373.26] khelper used greatest stack depth: 7548 bytes left [42949373.34] kworker/u:0 used greatest stack depth: 7324 bytes left [42949373.50] bio: create slab at 0 [42949373.63] kworker/u:0 used greatest stack depth: 7260 bytes left [42949374.63] kworker/u:0 used greatest stack depth: 7180 bytes left [42949375.25] VFS: Disk quotas dquot_6.5.2 [42949375.27] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [42949375.39] msgmni has been set to 16 [42949375.42] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [42949375.43] io scheduler noop registered [42949375.44] io scheduler deadline registered [42949375.46] io scheduler cfq registered (default) [42949375.49] Architecture Specific Serial Driver [42949375.50] ttyS0 at MMIO 0x40001000 (irq = 5) is a arch_uart [42949375.70] loop: module loaded [42949375.72] mice: PS/2 mouse device common for all mice [42949375.78] [ cut here ] [42949375.80] WARNING: at fs/proc/generic.c:589 .LBE364+0x0/0x2() [42949375.81] proc_dir_entry '/proc/schedstat' already registered [42949375.82] Modules linked in: [42949375.83] ---[ end trace 31baa4bbf69a8bbc ]--- [42949375.85] Failed to execute /init [42949375.87] 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
Re: Issue with ps -l command "Unknown HZ value! (744514) Assume 100."
Hi... On Thu, Aug 30, 2012 at 12:28 PM, KARTHIK SEKURU wrote: > > After the kernel bootup, in the command prompt when i am using the command > "ps -l "..i am getting the following > > sh-4.2# ps -l > Unknown HZ value! (744514) Assume 100. IIRC, if you run this at shell: getconf -a | grep TCK you will get (in x86 32 bit): CLK_TCK100 It means to me that 100 is assumed as "known value in user space". However, in reality, the real timer precision is based upon real HZ value in kernel. Regarding your "broken" HZ, i guess it is more a user space issue rather than kernel space. I check "man sysconf" and "man getconf", and I got impression that it is a value either stated in one of glibc headers or kernel headers. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
