Long Kernel Boot Segment in 18.04












0















I need help figuring out why the 1st "Kernel" section of boot time shown by "systemd-analyze plot" is 67 seconds long. How do I debug that part of the boot process?



I've been looking around and see a lot of posts discussing various things that either don't apply to my system or didn't make much difference.



-- apt-daily.service was running during boot so I followed instructions to create an override.conf file and removed it from the boot sequence. No real improvement, but it's not part of boot anymore.



-- I see reports about bugs in the 4.15.0-24 kernel but I run 4.15.0-43-generic.



-- I see discussions about swap partitions, but I don't have one. Posts I read say 18.04 uses swap files and they are just fine vs. having a swap partition.



-- When I run "systemd-analyze critical-chain" the first several entries (starting with "graphical.target") all end in @52.342s but I'm not sure what they mean.



-- The top several entries from "systemd-analyze blame" are



------- 31.636s for lightdm.service



------- 31.625s for plymouth-quit-wait.service



------- 14.750s for dev-sda1.device



------- 9.733s for systemd-journal-flush.service



------- and then it's keyboard, network, disks and stuff under 7 seconds each after that.



-- I like hibernation so I didn't play with the "noresume" setting in Grub.



This problem started when I decided to try 18.04 on a spare laptop. I reformatted the whole 750GB drive into one single EXT4 partition by rewriting the previous partition table. That worked fine and I installed 18.04 from a live CD.



I previously ran 16.04 and 18.04 on this same machine with no problems. The first version of 18.04 was an update from 16.04 but had functional problems. I decided to retry 18.04 as a clean install on a clean disk and that's when the speed problem started.



So, any ideas how to figure this out? I want to lend this laptop to a friend as a trial step into linux and having a long boot time like this will be a turn off for him.










share|improve this question



























    0















    I need help figuring out why the 1st "Kernel" section of boot time shown by "systemd-analyze plot" is 67 seconds long. How do I debug that part of the boot process?



    I've been looking around and see a lot of posts discussing various things that either don't apply to my system or didn't make much difference.



    -- apt-daily.service was running during boot so I followed instructions to create an override.conf file and removed it from the boot sequence. No real improvement, but it's not part of boot anymore.



    -- I see reports about bugs in the 4.15.0-24 kernel but I run 4.15.0-43-generic.



    -- I see discussions about swap partitions, but I don't have one. Posts I read say 18.04 uses swap files and they are just fine vs. having a swap partition.



    -- When I run "systemd-analyze critical-chain" the first several entries (starting with "graphical.target") all end in @52.342s but I'm not sure what they mean.



    -- The top several entries from "systemd-analyze blame" are



    ------- 31.636s for lightdm.service



    ------- 31.625s for plymouth-quit-wait.service



    ------- 14.750s for dev-sda1.device



    ------- 9.733s for systemd-journal-flush.service



    ------- and then it's keyboard, network, disks and stuff under 7 seconds each after that.



    -- I like hibernation so I didn't play with the "noresume" setting in Grub.



    This problem started when I decided to try 18.04 on a spare laptop. I reformatted the whole 750GB drive into one single EXT4 partition by rewriting the previous partition table. That worked fine and I installed 18.04 from a live CD.



    I previously ran 16.04 and 18.04 on this same machine with no problems. The first version of 18.04 was an update from 16.04 but had functional problems. I decided to retry 18.04 as a clean install on a clean disk and that's when the speed problem started.



    So, any ideas how to figure this out? I want to lend this laptop to a friend as a trial step into linux and having a long boot time like this will be a turn off for him.










    share|improve this question

























      0












      0








      0








      I need help figuring out why the 1st "Kernel" section of boot time shown by "systemd-analyze plot" is 67 seconds long. How do I debug that part of the boot process?



      I've been looking around and see a lot of posts discussing various things that either don't apply to my system or didn't make much difference.



      -- apt-daily.service was running during boot so I followed instructions to create an override.conf file and removed it from the boot sequence. No real improvement, but it's not part of boot anymore.



      -- I see reports about bugs in the 4.15.0-24 kernel but I run 4.15.0-43-generic.



      -- I see discussions about swap partitions, but I don't have one. Posts I read say 18.04 uses swap files and they are just fine vs. having a swap partition.



      -- When I run "systemd-analyze critical-chain" the first several entries (starting with "graphical.target") all end in @52.342s but I'm not sure what they mean.



      -- The top several entries from "systemd-analyze blame" are



      ------- 31.636s for lightdm.service



      ------- 31.625s for plymouth-quit-wait.service



      ------- 14.750s for dev-sda1.device



      ------- 9.733s for systemd-journal-flush.service



      ------- and then it's keyboard, network, disks and stuff under 7 seconds each after that.



      -- I like hibernation so I didn't play with the "noresume" setting in Grub.



      This problem started when I decided to try 18.04 on a spare laptop. I reformatted the whole 750GB drive into one single EXT4 partition by rewriting the previous partition table. That worked fine and I installed 18.04 from a live CD.



      I previously ran 16.04 and 18.04 on this same machine with no problems. The first version of 18.04 was an update from 16.04 but had functional problems. I decided to retry 18.04 as a clean install on a clean disk and that's when the speed problem started.



      So, any ideas how to figure this out? I want to lend this laptop to a friend as a trial step into linux and having a long boot time like this will be a turn off for him.










      share|improve this question














      I need help figuring out why the 1st "Kernel" section of boot time shown by "systemd-analyze plot" is 67 seconds long. How do I debug that part of the boot process?



      I've been looking around and see a lot of posts discussing various things that either don't apply to my system or didn't make much difference.



      -- apt-daily.service was running during boot so I followed instructions to create an override.conf file and removed it from the boot sequence. No real improvement, but it's not part of boot anymore.



      -- I see reports about bugs in the 4.15.0-24 kernel but I run 4.15.0-43-generic.



      -- I see discussions about swap partitions, but I don't have one. Posts I read say 18.04 uses swap files and they are just fine vs. having a swap partition.



      -- When I run "systemd-analyze critical-chain" the first several entries (starting with "graphical.target") all end in @52.342s but I'm not sure what they mean.



      -- The top several entries from "systemd-analyze blame" are



      ------- 31.636s for lightdm.service



      ------- 31.625s for plymouth-quit-wait.service



      ------- 14.750s for dev-sda1.device



      ------- 9.733s for systemd-journal-flush.service



      ------- and then it's keyboard, network, disks and stuff under 7 seconds each after that.



      -- I like hibernation so I didn't play with the "noresume" setting in Grub.



      This problem started when I decided to try 18.04 on a spare laptop. I reformatted the whole 750GB drive into one single EXT4 partition by rewriting the previous partition table. That worked fine and I installed 18.04 from a live CD.



      I previously ran 16.04 and 18.04 on this same machine with no problems. The first version of 18.04 was an update from 16.04 but had functional problems. I decided to retry 18.04 as a clean install on a clean disk and that's when the speed problem started.



      So, any ideas how to figure this out? I want to lend this laptop to a friend as a trial step into linux and having a long boot time like this will be a turn off for him.







      boot kernel






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 19 at 3:49









      user447969user447969

      1313




      1313






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Solved it.



          My computer is a Dell Inspiron 1520 and there is a bug in the kernel that affects those laptops. It tries to start an svideo adapter, which the laptop doesn't have.



          This post has the solution: Boot very slow because of drm_kms_helper errors



          The solution is to disable the svideo connector using grub at boot up.



          sudo nano /etc/default/grub



          Add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"



          sudo update-grub
          sudo reboot






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111033%2flong-kernel-boot-segment-in-18-04%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Solved it.



            My computer is a Dell Inspiron 1520 and there is a bug in the kernel that affects those laptops. It tries to start an svideo adapter, which the laptop doesn't have.



            This post has the solution: Boot very slow because of drm_kms_helper errors



            The solution is to disable the svideo connector using grub at boot up.



            sudo nano /etc/default/grub



            Add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"



            sudo update-grub
            sudo reboot






            share|improve this answer




























              0














              Solved it.



              My computer is a Dell Inspiron 1520 and there is a bug in the kernel that affects those laptops. It tries to start an svideo adapter, which the laptop doesn't have.



              This post has the solution: Boot very slow because of drm_kms_helper errors



              The solution is to disable the svideo connector using grub at boot up.



              sudo nano /etc/default/grub



              Add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"



              sudo update-grub
              sudo reboot






              share|improve this answer


























                0












                0








                0







                Solved it.



                My computer is a Dell Inspiron 1520 and there is a bug in the kernel that affects those laptops. It tries to start an svideo adapter, which the laptop doesn't have.



                This post has the solution: Boot very slow because of drm_kms_helper errors



                The solution is to disable the svideo connector using grub at boot up.



                sudo nano /etc/default/grub



                Add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"



                sudo update-grub
                sudo reboot






                share|improve this answer













                Solved it.



                My computer is a Dell Inspiron 1520 and there is a bug in the kernel that affects those laptops. It tries to start an svideo adapter, which the laptop doesn't have.



                This post has the solution: Boot very slow because of drm_kms_helper errors



                The solution is to disable the svideo connector using grub at boot up.



                sudo nano /etc/default/grub



                Add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"



                sudo update-grub
                sudo reboot







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 20 at 3:14









                user447969user447969

                1313




                1313






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111033%2flong-kernel-boot-segment-in-18-04%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?