Re: [SOLVED] Re: Very slow boot in F27 after recent update

[Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>]

On Tue, May 8, 2018 at 8:42 AM, Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx> wrote:

[snip]

 

Possibly before the update, chronyd and gssproxy (and I see also libvirtd) went into a sort of parallel background not preventing display manager login completion?

In fact in about 10-13 seconds (I have an SSD disk on the laptop) I had the gdm login page....

[g.cecchi@ope46 ~]$ sudo systemd-analyze time

Startup finished in 1.379s (kernel) + 1.965s (initrd) + 1min 49.668s (userspace) = 1min 53.012s

[g.cecchi@ope46 ~]$ 

[g.cecchi@ope46 ~]$ sudo systemd-analyze blame

    1min 30.134s gssproxy.service

    1min 15.937s chronyd.service

         30.043s NetworkManager-wait-online.service

         17.876s libvirtd.service

          1.102s dracut-initqueue.service

          1.015s lvm2-monitor.service

It seems latest updates have solved my problems, both if network cable is connected and without it.

I updated the system in the mean time several weeks ago to F28 and with yesterday update the problem arose again.

Same long elapsed times for gssproxy and chronyd and sendmail service starting and stopping several times.

Booting with the previous kernel lets the problem disappear, apparently

Good last kernel:  4.16.16-300.fc28.x86_64

Bad new kernel: 4.17.2-200.fc28.x86_64

$ sudo dnf history list | head -6 

ID     | Command line             | Date and time    | Action(s)      | Altered

-------------------------------------------------------------------------------

   353 | update                   | 2018-06-25 09:00 | E, I, U        |  209 EE

   352 | update                   | 2018-06-20 20:52 | E, I, O, U     |  261 EE

   351 | update                   | 2018-06-16 13:32 | E, I, U        |   89 EE

   350 | update                   | 2018-06-14 09:23 | Update         |   29   

$ 

Also the shutdown phase yesterday was very slow.

Is there a command to analyse shutdown steps, as you make with boot and  "systemd-analyze blame" command?

Anyone else?

Gianluca

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/Y4PDLKSU6QL7FLGDXQ73SOKAPEBUKBXA/