Hi Team. Recently I installed fedora 19, 64 bit on my machine. MAchine information is as follows.
P5KC motherboard. 8GB (ddr2), Q6500 cpu.
Boot line is as follows.
linux /vmlinuz-3.10.3-300.fc19.x86_64 root=/dev/mapper/vg_2-lv_root ro rootfstype=ext4 rd.md=0 rd.lvm.lv=vg_1/lv_swap rd.dm=0 vconsole.keymap=us rd.lvm.lv=vg_2/lv_root rd.luks=0 vconsole.font=latarcyrheb-sun16 quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off libahci.ignore_sss=1 raid=noautodetect LANG=en_US.UTF-8
My problem is during boot network and related stuff takes too long. Interface comes up fast, but somthing called network drop minotor takes hell of a time. (5+ seconda always.)
Here is systemd-analyze blame. This was never a problem on fedora 18. I am also not sure how to disable this network drop monitor stuff. (By the way I have disabled all services that I dont need) The only problem is this network drop monitor.
Here are the logs from messages. Clearly showing gap of seconds between network drop monitor beng started and interface coming up.
[root@anilraj24 .freerdp]# systemd-analyze
Startup finished in 853ms (kernel) + 1.702s (initrd) + 13.009s (userspace) = 15.565s
[root@anilraj24 .freerdp]# dmesg|grep network
[ 0.380342] drop_monitor: Initializing network drop monitor service
[ 3.589180] systemd-udevd[380]: renamed network interface eth0 to em1
Jul 28 08:11:41 anilraj24 kernel: [ 0.380342] drop_monitor: Initializing network drop monitor service
Jul 28 08:11:51 anilraj24 systemd[1]: Started LSB: Bring up/down networking.
Jul 28 08:11:51 anilraj24 network[528]: Bringing up loopback interface: [ OK ]
Jul 28 08:11:51 anilraj24 network[528]: Bringing up interface em1: [ OK ]
Gap of 11 seconds!!
systemd-anayze blame -- (top 5)
[root@anilraj24 .freerdp]# systemd-analyze blame
9.651s network.service
5.037s akmods-shutdown.service
3.015s akmods.service
1.040s plymouth-start.service
322ms polkit.service
[root@anilraj24 .freerdp]# systemd-analyze
Startup finished in 853ms (kernel) + 1.702s (initrd) + 13.009s (userspace) = 15.565s
Thank you in advance.
P5KC motherboard. 8GB (ddr2), Q6500 cpu.
Boot line is as follows.
linux /vmlinuz-3.10.3-300.fc19.x86_64 root=/dev/mapper/vg_2-lv_root ro rootfstype=ext4 rd.md=0 rd.lvm.lv=vg_1/lv_swap rd.dm=0 vconsole.keymap=us rd.lvm.lv=vg_2/lv_root rd.luks=0 vconsole.font=latarcyrheb-sun16 quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off libahci.ignore_sss=1 raid=noautodetect LANG=en_US.UTF-8
My problem is during boot network and related stuff takes too long. Interface comes up fast, but somthing called network drop minotor takes hell of a time. (5+ seconda always.)
Here is systemd-analyze blame. This was never a problem on fedora 18. I am also not sure how to disable this network drop monitor stuff. (By the way I have disabled all services that I dont need) The only problem is this network drop monitor.
Here are the logs from messages. Clearly showing gap of seconds between network drop monitor beng started and interface coming up.
[root@anilraj24 .freerdp]# systemd-analyze
Startup finished in 853ms (kernel) + 1.702s (initrd) + 13.009s (userspace) = 15.565s
[root@anilraj24 .freerdp]# dmesg|grep network
[ 0.380342] drop_monitor: Initializing network drop monitor service
[ 3.589180] systemd-udevd[380]: renamed network interface eth0 to em1
Jul 28 08:11:41 anilraj24 kernel: [ 0.380342] drop_monitor: Initializing network drop monitor service
Jul 28 08:11:51 anilraj24 systemd[1]: Started LSB: Bring up/down networking.
Jul 28 08:11:51 anilraj24 network[528]: Bringing up loopback interface: [ OK ]
Jul 28 08:11:51 anilraj24 network[528]: Bringing up interface em1: [ OK ]
Gap of 11 seconds!!
systemd-anayze blame -- (top 5)
[root@anilraj24 .freerdp]# systemd-analyze blame
9.651s network.service
5.037s akmods-shutdown.service
3.015s akmods.service
1.040s plymouth-start.service
322ms polkit.service
[root@anilraj24 .freerdp]# systemd-analyze
Startup finished in 853ms (kernel) + 1.702s (initrd) + 13.009s (userspace) = 15.565s
Thank you in advance.