Long kernel load timeXubuntu 18.04 kernel takes long to bootDisable Ethernet permanently to speed up boot timeHigh boottime - Big gaps in dmesgCPU getting stuck during boot due to nvidia driverSlow boot time (Xubuntu 18.04)Slow boot 18.04 (init ramdisk)Why remounting root file system takes a lot of time?

Did any astronauts on a mission complain about waking up?

How to get best taste out of tomatoes?

Nominally, he has only half a life at 59! - British cryptic crossword question

How can I prevent renaming the arguments to Function[...,...] for making plots of spherical harmonics coloured by phase

LACPDU packets to pass through unmanaged switch

Definition of NMR peak

Does a small cup of coffee result in a 45% reduced blood flow to the brain?

Christmas party and autism

I'm from Mumbai, India. I want to travel to Europe as a tourist but my salary is low ( €190/month)

Run -E without sudo

Why would a life company agree to a 20-year guaranteed life annuity which is expected to pay out more than the principal?

Is there a coup going on in Bolivia?

Why is this claimed dereferencing type-punned pointer warning compiler-specific?

Plot the Pascalian triangle

Three button calculator

Opening Moves: Pawn Chains and Countering Attacks

Can the jeopardy of being judged be fought against in court?

Paint Exterior Door that is in Sun

Why is the Exchange French considered drawish?

Numeric example to understand the effect of option gamma

Get verbatim output of 'curl wttr.in' in org src code

Is it possible to produce a field with three operations?

Is camera at risk of condensation in cold temperatures if never removed from bag?

How to test oom-killer from command line



Long kernel load time


Xubuntu 18.04 kernel takes long to bootDisable Ethernet permanently to speed up boot timeHigh boottime - Big gaps in dmesgCPU getting stuck during boot due to nvidia driverSlow boot time (Xubuntu 18.04)Slow boot 18.04 (init ramdisk)Why remounting root file system takes a lot of time?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









2

















Running Ubuntu 18.04 on a Dell XPS 9370, I'm getting kernel load times of over 30 seconds.



systemd-analyze output:



Startup finished in 12.834s (firmware) + 1.331s (loader) + 33.643s (kernel) + 11.692s (userspace) = 59.502s


systemd-analyze blame only shows userspace load times, so I wont include it here.



Relevant dmesg output:



[ 5.154052] pcieport 0000:04:00.0: Refused to change power state, currently in D3
[ 5.155956] pci_bus 0000:05: busn_res: [bus 05] is released
[ 5.156127] pci_bus 0000:06: busn_res: [bus 06-38] is released
[ 5.156235] pci_bus 0000:39: busn_res: [bus 39] is released
[ 5.156300] pci_bus 0000:3a: busn_res: [bus 3a-6d] is released
[ 5.156352] pci_bus 0000:04: busn_res: [bus 04-6d] is released
[ 33.556238] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)


Full dmesg output: https://pastebin.com/0JmWuLtZ



I've tried editing /etc/initramfs-tools/conf.d/resume as described here and adding noresume to my GRUB_CMDLINE_LINUX_DEFAULT.



How can I troubleshoot this?










share|improve this question


























  • BTW there are tricks to reducing Firmware time too.

    – WinEunuuchs2Unix
    Aug 10 at 4:08











  • @WinEunuuchs2Unix Ooh, I'll have a look.

    – Omegastick
    Aug 10 at 4:13

















2

















Running Ubuntu 18.04 on a Dell XPS 9370, I'm getting kernel load times of over 30 seconds.



systemd-analyze output:



Startup finished in 12.834s (firmware) + 1.331s (loader) + 33.643s (kernel) + 11.692s (userspace) = 59.502s


systemd-analyze blame only shows userspace load times, so I wont include it here.



Relevant dmesg output:



[ 5.154052] pcieport 0000:04:00.0: Refused to change power state, currently in D3
[ 5.155956] pci_bus 0000:05: busn_res: [bus 05] is released
[ 5.156127] pci_bus 0000:06: busn_res: [bus 06-38] is released
[ 5.156235] pci_bus 0000:39: busn_res: [bus 39] is released
[ 5.156300] pci_bus 0000:3a: busn_res: [bus 3a-6d] is released
[ 5.156352] pci_bus 0000:04: busn_res: [bus 04-6d] is released
[ 33.556238] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)


Full dmesg output: https://pastebin.com/0JmWuLtZ



I've tried editing /etc/initramfs-tools/conf.d/resume as described here and adding noresume to my GRUB_CMDLINE_LINUX_DEFAULT.



How can I troubleshoot this?










share|improve this question


























  • BTW there are tricks to reducing Firmware time too.

    – WinEunuuchs2Unix
    Aug 10 at 4:08











  • @WinEunuuchs2Unix Ooh, I'll have a look.

    – Omegastick
    Aug 10 at 4:13













2












2








2








Running Ubuntu 18.04 on a Dell XPS 9370, I'm getting kernel load times of over 30 seconds.



systemd-analyze output:



Startup finished in 12.834s (firmware) + 1.331s (loader) + 33.643s (kernel) + 11.692s (userspace) = 59.502s


systemd-analyze blame only shows userspace load times, so I wont include it here.



Relevant dmesg output:



[ 5.154052] pcieport 0000:04:00.0: Refused to change power state, currently in D3
[ 5.155956] pci_bus 0000:05: busn_res: [bus 05] is released
[ 5.156127] pci_bus 0000:06: busn_res: [bus 06-38] is released
[ 5.156235] pci_bus 0000:39: busn_res: [bus 39] is released
[ 5.156300] pci_bus 0000:3a: busn_res: [bus 3a-6d] is released
[ 5.156352] pci_bus 0000:04: busn_res: [bus 04-6d] is released
[ 33.556238] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)


Full dmesg output: https://pastebin.com/0JmWuLtZ



I've tried editing /etc/initramfs-tools/conf.d/resume as described here and adding noresume to my GRUB_CMDLINE_LINUX_DEFAULT.



How can I troubleshoot this?










share|improve this question















Running Ubuntu 18.04 on a Dell XPS 9370, I'm getting kernel load times of over 30 seconds.



systemd-analyze output:



Startup finished in 12.834s (firmware) + 1.331s (loader) + 33.643s (kernel) + 11.692s (userspace) = 59.502s


systemd-analyze blame only shows userspace load times, so I wont include it here.



Relevant dmesg output:



[ 5.154052] pcieport 0000:04:00.0: Refused to change power state, currently in D3
[ 5.155956] pci_bus 0000:05: busn_res: [bus 05] is released
[ 5.156127] pci_bus 0000:06: busn_res: [bus 06-38] is released
[ 5.156235] pci_bus 0000:39: busn_res: [bus 39] is released
[ 5.156300] pci_bus 0000:3a: busn_res: [bus 3a-6d] is released
[ 5.156352] pci_bus 0000:04: busn_res: [bus 04-6d] is released
[ 33.556238] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)


Full dmesg output: https://pastebin.com/0JmWuLtZ



I've tried editing /etc/initramfs-tools/conf.d/resume as described here and adding noresume to my GRUB_CMDLINE_LINUX_DEFAULT.



How can I troubleshoot this?







boot 18.04 kernel performance systemd






share|improve this question














share|improve this question











share|improve this question




share|improve this question










asked Aug 9 at 16:32









OmegastickOmegastick

1335 bronze badges




1335 bronze badges















  • BTW there are tricks to reducing Firmware time too.

    – WinEunuuchs2Unix
    Aug 10 at 4:08











  • @WinEunuuchs2Unix Ooh, I'll have a look.

    – Omegastick
    Aug 10 at 4:13

















  • BTW there are tricks to reducing Firmware time too.

    – WinEunuuchs2Unix
    Aug 10 at 4:08











  • @WinEunuuchs2Unix Ooh, I'll have a look.

    – Omegastick
    Aug 10 at 4:13
















BTW there are tricks to reducing Firmware time too.

– WinEunuuchs2Unix
Aug 10 at 4:08





BTW there are tricks to reducing Firmware time too.

– WinEunuuchs2Unix
Aug 10 at 4:08













@WinEunuuchs2Unix Ooh, I'll have a look.

– Omegastick
Aug 10 at 4:13





@WinEunuuchs2Unix Ooh, I'll have a look.

– Omegastick
Aug 10 at 4:13










2 Answers
2






active

oldest

votes


















2


















I had disabled Intel SpeedStep® Technology in the BIOS, which was preventing the CPU from switching power states. Enabling it brought the kernel load time to about 3 seconds.






share|improve this answer

































    2



















    How can I troubleshoot this?






    The first step is to find out what PCI device is generating the error:




    pcieport 0000:04:00.0: Refused to change power state, currently in D3



    My system doesn't have a 0000:04:00.0 but it does have 0000:03:00.0 so I would use:



    $ cd /sys/bus/pci/devices/0000:03:00.0

    $ ls -la
    total 0
    drwxr-xr-x 5 root root 0 Aug 8 17:15 .
    drwxr-xr-x 8 root root 0 Aug 8 17:15 ..
    drwxr-xr-x 3 root root 0 Aug 9 17:53 0000:03:00.0:pcie208
    -rw-r--r-- 1 root root 4096 Aug 9 17:53 broken_parity_status
    -r--r--r-- 1 root root 4096 Aug 8 17:15 class
    -rw-r--r-- 1 root root 4096 Aug 8 17:15 config
    -r--r--r-- 1 root root 4096 Aug 9 17:53 consistent_dma_mask_bits
    -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_speed
    -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_width
    -rw-r--r-- 1 root root 4096 Aug 9 17:53 d3cold_allowed
    -r--r--r-- 1 root root 4096 Aug 8 17:15 device
    -r--r--r-- 1 root root 4096 Aug 9 17:53 dma_mask_bits
    lrwxrwxrwx 1 root root 0 Aug 8 17:15 driver -> ../../../../../bus/pci/drivers/pcieport
    -rw-r--r-- 1 root root 4096 Aug 9 17:53 driver_override
    -rw-r--r-- 1 root root 4096 Aug 9 17:53 enable
    -r--r--r-- 1 root root 4096 Aug 8 17:15 irq
    -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpulist
    -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpus
    -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_speed
    -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_width
    -r--r--r-- 1 root root 4096 Aug 9 17:53 modalias
    -rw-r--r-- 1 root root 4096 Aug 9 17:53 msi_bus
    -rw-r--r-- 1 root root 4096 Aug 9 17:53 numa_node
    drwxr-xr-x 3 root root 0 Aug 9 17:53 pci_bus
    drwxr-xr-x 2 root root 0 Aug 8 17:15 power
    --w--w---- 1 root root 4096 Aug 9 17:53 remove
    --w--w---- 1 root root 4096 Aug 9 17:53 rescan
    -r--r--r-- 1 root root 4096 Aug 8 17:15 resource
    -r--r--r-- 1 root root 4096 Aug 9 17:53 revision
    -r--r--r-- 1 root root 4096 Aug 9 17:53 secondary_bus_number
    -r--r--r-- 1 root root 4096 Aug 9 17:53 subordinate_bus_number
    lrwxrwxrwx 1 root root 0 Aug 9 17:53 subsystem -> ../../../../../bus/pci
    -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_device
    -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_vendor
    -rw-r--r-- 1 root root 4096 Aug 9 17:53 uevent
    -r--r--r-- 1 root root 4096 Aug 8 17:15 vendor

    $ cat vendor
    0x8086

    $ cat device
    0x1576

    $ cat class
    0x060400

    $ cat max_link_speed
    2.5 GT/s

    $ cat max_link_width
    4

    $ lspci -n | tail -8
    03:00.0 0604: 8086:1576
    03:01.0 0604: 8086:1576
    03:02.0 0604: 8086:1576
    39:00.0 0c03: 8086:15b5
    3b:00.0 0200: 1969:e0a1 (rev 10)
    3c:00.0 0280: 168c:003e (rev 32)
    3d:00.0 ff00: 10ec:5227 (rev 01)
    3e:00.0 0108: 144d:a804

    $ lspci | tail -8
    03:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
    03:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
    03:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
    39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge]
    3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
    3c:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
    3d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
    3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961


    If my system had the error then it would be caused by the Thunderbolt subsystem and I might just start by unplugging my Thunderbolt DPI to HDMI adapter.



    In your case replace 0000:03:00.0 with 0000:04:00.0 above. Adjust tail number of lines as necessary.



    This is the first step in trouble shooting.



    Credit: - Decoding PCI data and lspci output on Linux hosts




    Solution: It was Intel SpeedStep located at 0000:04:00.0 and enabling it in BIOS removes 30 second boot delay.






    share|improve this answer




























    • This helped me find the problem. I've posted the root cause as a separate answer.

      – Omegastick
      Aug 10 at 3:50











    • @Omegastick Awesome! I upvoted your answer. I don't have Intel SpeedStep® Technology on my system which explains how you have a 0000:04:00.0 where my PCI ends at 0000:03:00.0

      – WinEunuuchs2Unix
      Aug 10 at 4:03











    • Quick correction, I had to enable it to remove the delay.

      – Omegastick
      Aug 10 at 4:12











    • @Omegastick I did a quick edit. Changed "disabling" to "enabling"

      – WinEunuuchs2Unix
      Aug 10 at 14:59












    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/4.0/"u003ecc by-sa 4.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%2f1164632%2flong-kernel-load-time%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown


























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2


















    I had disabled Intel SpeedStep® Technology in the BIOS, which was preventing the CPU from switching power states. Enabling it brought the kernel load time to about 3 seconds.






    share|improve this answer






























      2


















      I had disabled Intel SpeedStep® Technology in the BIOS, which was preventing the CPU from switching power states. Enabling it brought the kernel load time to about 3 seconds.






      share|improve this answer




























        2














        2










        2









        I had disabled Intel SpeedStep® Technology in the BIOS, which was preventing the CPU from switching power states. Enabling it brought the kernel load time to about 3 seconds.






        share|improve this answer














        I had disabled Intel SpeedStep® Technology in the BIOS, which was preventing the CPU from switching power states. Enabling it brought the kernel load time to about 3 seconds.







        share|improve this answer













        share|improve this answer




        share|improve this answer










        answered Aug 10 at 3:49









        OmegastickOmegastick

        1335 bronze badges




        1335 bronze badges


























            2



















            How can I troubleshoot this?






            The first step is to find out what PCI device is generating the error:




            pcieport 0000:04:00.0: Refused to change power state, currently in D3



            My system doesn't have a 0000:04:00.0 but it does have 0000:03:00.0 so I would use:



            $ cd /sys/bus/pci/devices/0000:03:00.0

            $ ls -la
            total 0
            drwxr-xr-x 5 root root 0 Aug 8 17:15 .
            drwxr-xr-x 8 root root 0 Aug 8 17:15 ..
            drwxr-xr-x 3 root root 0 Aug 9 17:53 0000:03:00.0:pcie208
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 broken_parity_status
            -r--r--r-- 1 root root 4096 Aug 8 17:15 class
            -rw-r--r-- 1 root root 4096 Aug 8 17:15 config
            -r--r--r-- 1 root root 4096 Aug 9 17:53 consistent_dma_mask_bits
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_width
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 d3cold_allowed
            -r--r--r-- 1 root root 4096 Aug 8 17:15 device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 dma_mask_bits
            lrwxrwxrwx 1 root root 0 Aug 8 17:15 driver -> ../../../../../bus/pci/drivers/pcieport
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 driver_override
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 enable
            -r--r--r-- 1 root root 4096 Aug 8 17:15 irq
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpulist
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpus
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_width
            -r--r--r-- 1 root root 4096 Aug 9 17:53 modalias
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 msi_bus
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 numa_node
            drwxr-xr-x 3 root root 0 Aug 9 17:53 pci_bus
            drwxr-xr-x 2 root root 0 Aug 8 17:15 power
            --w--w---- 1 root root 4096 Aug 9 17:53 remove
            --w--w---- 1 root root 4096 Aug 9 17:53 rescan
            -r--r--r-- 1 root root 4096 Aug 8 17:15 resource
            -r--r--r-- 1 root root 4096 Aug 9 17:53 revision
            -r--r--r-- 1 root root 4096 Aug 9 17:53 secondary_bus_number
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subordinate_bus_number
            lrwxrwxrwx 1 root root 0 Aug 9 17:53 subsystem -> ../../../../../bus/pci
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_vendor
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 uevent
            -r--r--r-- 1 root root 4096 Aug 8 17:15 vendor

            $ cat vendor
            0x8086

            $ cat device
            0x1576

            $ cat class
            0x060400

            $ cat max_link_speed
            2.5 GT/s

            $ cat max_link_width
            4

            $ lspci -n | tail -8
            03:00.0 0604: 8086:1576
            03:01.0 0604: 8086:1576
            03:02.0 0604: 8086:1576
            39:00.0 0c03: 8086:15b5
            3b:00.0 0200: 1969:e0a1 (rev 10)
            3c:00.0 0280: 168c:003e (rev 32)
            3d:00.0 ff00: 10ec:5227 (rev 01)
            3e:00.0 0108: 144d:a804

            $ lspci | tail -8
            03:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge]
            3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
            3c:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
            3d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
            3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961


            If my system had the error then it would be caused by the Thunderbolt subsystem and I might just start by unplugging my Thunderbolt DPI to HDMI adapter.



            In your case replace 0000:03:00.0 with 0000:04:00.0 above. Adjust tail number of lines as necessary.



            This is the first step in trouble shooting.



            Credit: - Decoding PCI data and lspci output on Linux hosts




            Solution: It was Intel SpeedStep located at 0000:04:00.0 and enabling it in BIOS removes 30 second boot delay.






            share|improve this answer




























            • This helped me find the problem. I've posted the root cause as a separate answer.

              – Omegastick
              Aug 10 at 3:50











            • @Omegastick Awesome! I upvoted your answer. I don't have Intel SpeedStep® Technology on my system which explains how you have a 0000:04:00.0 where my PCI ends at 0000:03:00.0

              – WinEunuuchs2Unix
              Aug 10 at 4:03











            • Quick correction, I had to enable it to remove the delay.

              – Omegastick
              Aug 10 at 4:12











            • @Omegastick I did a quick edit. Changed "disabling" to "enabling"

              – WinEunuuchs2Unix
              Aug 10 at 14:59















            2



















            How can I troubleshoot this?






            The first step is to find out what PCI device is generating the error:




            pcieport 0000:04:00.0: Refused to change power state, currently in D3



            My system doesn't have a 0000:04:00.0 but it does have 0000:03:00.0 so I would use:



            $ cd /sys/bus/pci/devices/0000:03:00.0

            $ ls -la
            total 0
            drwxr-xr-x 5 root root 0 Aug 8 17:15 .
            drwxr-xr-x 8 root root 0 Aug 8 17:15 ..
            drwxr-xr-x 3 root root 0 Aug 9 17:53 0000:03:00.0:pcie208
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 broken_parity_status
            -r--r--r-- 1 root root 4096 Aug 8 17:15 class
            -rw-r--r-- 1 root root 4096 Aug 8 17:15 config
            -r--r--r-- 1 root root 4096 Aug 9 17:53 consistent_dma_mask_bits
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_width
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 d3cold_allowed
            -r--r--r-- 1 root root 4096 Aug 8 17:15 device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 dma_mask_bits
            lrwxrwxrwx 1 root root 0 Aug 8 17:15 driver -> ../../../../../bus/pci/drivers/pcieport
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 driver_override
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 enable
            -r--r--r-- 1 root root 4096 Aug 8 17:15 irq
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpulist
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpus
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_width
            -r--r--r-- 1 root root 4096 Aug 9 17:53 modalias
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 msi_bus
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 numa_node
            drwxr-xr-x 3 root root 0 Aug 9 17:53 pci_bus
            drwxr-xr-x 2 root root 0 Aug 8 17:15 power
            --w--w---- 1 root root 4096 Aug 9 17:53 remove
            --w--w---- 1 root root 4096 Aug 9 17:53 rescan
            -r--r--r-- 1 root root 4096 Aug 8 17:15 resource
            -r--r--r-- 1 root root 4096 Aug 9 17:53 revision
            -r--r--r-- 1 root root 4096 Aug 9 17:53 secondary_bus_number
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subordinate_bus_number
            lrwxrwxrwx 1 root root 0 Aug 9 17:53 subsystem -> ../../../../../bus/pci
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_vendor
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 uevent
            -r--r--r-- 1 root root 4096 Aug 8 17:15 vendor

            $ cat vendor
            0x8086

            $ cat device
            0x1576

            $ cat class
            0x060400

            $ cat max_link_speed
            2.5 GT/s

            $ cat max_link_width
            4

            $ lspci -n | tail -8
            03:00.0 0604: 8086:1576
            03:01.0 0604: 8086:1576
            03:02.0 0604: 8086:1576
            39:00.0 0c03: 8086:15b5
            3b:00.0 0200: 1969:e0a1 (rev 10)
            3c:00.0 0280: 168c:003e (rev 32)
            3d:00.0 ff00: 10ec:5227 (rev 01)
            3e:00.0 0108: 144d:a804

            $ lspci | tail -8
            03:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge]
            3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
            3c:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
            3d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
            3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961


            If my system had the error then it would be caused by the Thunderbolt subsystem and I might just start by unplugging my Thunderbolt DPI to HDMI adapter.



            In your case replace 0000:03:00.0 with 0000:04:00.0 above. Adjust tail number of lines as necessary.



            This is the first step in trouble shooting.



            Credit: - Decoding PCI data and lspci output on Linux hosts




            Solution: It was Intel SpeedStep located at 0000:04:00.0 and enabling it in BIOS removes 30 second boot delay.






            share|improve this answer




























            • This helped me find the problem. I've posted the root cause as a separate answer.

              – Omegastick
              Aug 10 at 3:50











            • @Omegastick Awesome! I upvoted your answer. I don't have Intel SpeedStep® Technology on my system which explains how you have a 0000:04:00.0 where my PCI ends at 0000:03:00.0

              – WinEunuuchs2Unix
              Aug 10 at 4:03











            • Quick correction, I had to enable it to remove the delay.

              – Omegastick
              Aug 10 at 4:12











            • @Omegastick I did a quick edit. Changed "disabling" to "enabling"

              – WinEunuuchs2Unix
              Aug 10 at 14:59













            2














            2










            2










            How can I troubleshoot this?






            The first step is to find out what PCI device is generating the error:




            pcieport 0000:04:00.0: Refused to change power state, currently in D3



            My system doesn't have a 0000:04:00.0 but it does have 0000:03:00.0 so I would use:



            $ cd /sys/bus/pci/devices/0000:03:00.0

            $ ls -la
            total 0
            drwxr-xr-x 5 root root 0 Aug 8 17:15 .
            drwxr-xr-x 8 root root 0 Aug 8 17:15 ..
            drwxr-xr-x 3 root root 0 Aug 9 17:53 0000:03:00.0:pcie208
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 broken_parity_status
            -r--r--r-- 1 root root 4096 Aug 8 17:15 class
            -rw-r--r-- 1 root root 4096 Aug 8 17:15 config
            -r--r--r-- 1 root root 4096 Aug 9 17:53 consistent_dma_mask_bits
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_width
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 d3cold_allowed
            -r--r--r-- 1 root root 4096 Aug 8 17:15 device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 dma_mask_bits
            lrwxrwxrwx 1 root root 0 Aug 8 17:15 driver -> ../../../../../bus/pci/drivers/pcieport
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 driver_override
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 enable
            -r--r--r-- 1 root root 4096 Aug 8 17:15 irq
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpulist
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpus
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_width
            -r--r--r-- 1 root root 4096 Aug 9 17:53 modalias
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 msi_bus
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 numa_node
            drwxr-xr-x 3 root root 0 Aug 9 17:53 pci_bus
            drwxr-xr-x 2 root root 0 Aug 8 17:15 power
            --w--w---- 1 root root 4096 Aug 9 17:53 remove
            --w--w---- 1 root root 4096 Aug 9 17:53 rescan
            -r--r--r-- 1 root root 4096 Aug 8 17:15 resource
            -r--r--r-- 1 root root 4096 Aug 9 17:53 revision
            -r--r--r-- 1 root root 4096 Aug 9 17:53 secondary_bus_number
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subordinate_bus_number
            lrwxrwxrwx 1 root root 0 Aug 9 17:53 subsystem -> ../../../../../bus/pci
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_vendor
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 uevent
            -r--r--r-- 1 root root 4096 Aug 8 17:15 vendor

            $ cat vendor
            0x8086

            $ cat device
            0x1576

            $ cat class
            0x060400

            $ cat max_link_speed
            2.5 GT/s

            $ cat max_link_width
            4

            $ lspci -n | tail -8
            03:00.0 0604: 8086:1576
            03:01.0 0604: 8086:1576
            03:02.0 0604: 8086:1576
            39:00.0 0c03: 8086:15b5
            3b:00.0 0200: 1969:e0a1 (rev 10)
            3c:00.0 0280: 168c:003e (rev 32)
            3d:00.0 ff00: 10ec:5227 (rev 01)
            3e:00.0 0108: 144d:a804

            $ lspci | tail -8
            03:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge]
            3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
            3c:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
            3d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
            3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961


            If my system had the error then it would be caused by the Thunderbolt subsystem and I might just start by unplugging my Thunderbolt DPI to HDMI adapter.



            In your case replace 0000:03:00.0 with 0000:04:00.0 above. Adjust tail number of lines as necessary.



            This is the first step in trouble shooting.



            Credit: - Decoding PCI data and lspci output on Linux hosts




            Solution: It was Intel SpeedStep located at 0000:04:00.0 and enabling it in BIOS removes 30 second boot delay.






            share|improve this answer

















            How can I troubleshoot this?






            The first step is to find out what PCI device is generating the error:




            pcieport 0000:04:00.0: Refused to change power state, currently in D3



            My system doesn't have a 0000:04:00.0 but it does have 0000:03:00.0 so I would use:



            $ cd /sys/bus/pci/devices/0000:03:00.0

            $ ls -la
            total 0
            drwxr-xr-x 5 root root 0 Aug 8 17:15 .
            drwxr-xr-x 8 root root 0 Aug 8 17:15 ..
            drwxr-xr-x 3 root root 0 Aug 9 17:53 0000:03:00.0:pcie208
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 broken_parity_status
            -r--r--r-- 1 root root 4096 Aug 8 17:15 class
            -rw-r--r-- 1 root root 4096 Aug 8 17:15 config
            -r--r--r-- 1 root root 4096 Aug 9 17:53 consistent_dma_mask_bits
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 current_link_width
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 d3cold_allowed
            -r--r--r-- 1 root root 4096 Aug 8 17:15 device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 dma_mask_bits
            lrwxrwxrwx 1 root root 0 Aug 8 17:15 driver -> ../../../../../bus/pci/drivers/pcieport
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 driver_override
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 enable
            -r--r--r-- 1 root root 4096 Aug 8 17:15 irq
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpulist
            -r--r--r-- 1 root root 4096 Aug 9 17:53 local_cpus
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_speed
            -r--r--r-- 1 root root 4096 Aug 9 17:53 max_link_width
            -r--r--r-- 1 root root 4096 Aug 9 17:53 modalias
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 msi_bus
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 numa_node
            drwxr-xr-x 3 root root 0 Aug 9 17:53 pci_bus
            drwxr-xr-x 2 root root 0 Aug 8 17:15 power
            --w--w---- 1 root root 4096 Aug 9 17:53 remove
            --w--w---- 1 root root 4096 Aug 9 17:53 rescan
            -r--r--r-- 1 root root 4096 Aug 8 17:15 resource
            -r--r--r-- 1 root root 4096 Aug 9 17:53 revision
            -r--r--r-- 1 root root 4096 Aug 9 17:53 secondary_bus_number
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subordinate_bus_number
            lrwxrwxrwx 1 root root 0 Aug 9 17:53 subsystem -> ../../../../../bus/pci
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_device
            -r--r--r-- 1 root root 4096 Aug 9 17:53 subsystem_vendor
            -rw-r--r-- 1 root root 4096 Aug 9 17:53 uevent
            -r--r--r-- 1 root root 4096 Aug 8 17:15 vendor

            $ cat vendor
            0x8086

            $ cat device
            0x1576

            $ cat class
            0x060400

            $ cat max_link_speed
            2.5 GT/s

            $ cat max_link_width
            4

            $ lspci -n | tail -8
            03:00.0 0604: 8086:1576
            03:01.0 0604: 8086:1576
            03:02.0 0604: 8086:1576
            39:00.0 0c03: 8086:15b5
            3b:00.0 0200: 1969:e0a1 (rev 10)
            3c:00.0 0280: 168c:003e (rev 32)
            3d:00.0 ff00: 10ec:5227 (rev 01)
            3e:00.0 0108: 144d:a804

            $ lspci | tail -8
            03:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            03:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
            39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge]
            3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
            3c:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
            3d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
            3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961


            If my system had the error then it would be caused by the Thunderbolt subsystem and I might just start by unplugging my Thunderbolt DPI to HDMI adapter.



            In your case replace 0000:03:00.0 with 0000:04:00.0 above. Adjust tail number of lines as necessary.



            This is the first step in trouble shooting.



            Credit: - Decoding PCI data and lspci output on Linux hosts




            Solution: It was Intel SpeedStep located at 0000:04:00.0 and enabling it in BIOS removes 30 second boot delay.







            share|improve this answer















            share|improve this answer




            share|improve this answer








            edited Aug 10 at 14:59

























            answered Aug 10 at 0:24









            WinEunuuchs2UnixWinEunuuchs2Unix

            61k18 gold badges123 silver badges237 bronze badges




            61k18 gold badges123 silver badges237 bronze badges















            • This helped me find the problem. I've posted the root cause as a separate answer.

              – Omegastick
              Aug 10 at 3:50











            • @Omegastick Awesome! I upvoted your answer. I don't have Intel SpeedStep® Technology on my system which explains how you have a 0000:04:00.0 where my PCI ends at 0000:03:00.0

              – WinEunuuchs2Unix
              Aug 10 at 4:03











            • Quick correction, I had to enable it to remove the delay.

              – Omegastick
              Aug 10 at 4:12











            • @Omegastick I did a quick edit. Changed "disabling" to "enabling"

              – WinEunuuchs2Unix
              Aug 10 at 14:59

















            • This helped me find the problem. I've posted the root cause as a separate answer.

              – Omegastick
              Aug 10 at 3:50











            • @Omegastick Awesome! I upvoted your answer. I don't have Intel SpeedStep® Technology on my system which explains how you have a 0000:04:00.0 where my PCI ends at 0000:03:00.0

              – WinEunuuchs2Unix
              Aug 10 at 4:03











            • Quick correction, I had to enable it to remove the delay.

              – Omegastick
              Aug 10 at 4:12











            • @Omegastick I did a quick edit. Changed "disabling" to "enabling"

              – WinEunuuchs2Unix
              Aug 10 at 14:59
















            This helped me find the problem. I've posted the root cause as a separate answer.

            – Omegastick
            Aug 10 at 3:50





            This helped me find the problem. I've posted the root cause as a separate answer.

            – Omegastick
            Aug 10 at 3:50













            @Omegastick Awesome! I upvoted your answer. I don't have Intel SpeedStep® Technology on my system which explains how you have a 0000:04:00.0 where my PCI ends at 0000:03:00.0

            – WinEunuuchs2Unix
            Aug 10 at 4:03





            @Omegastick Awesome! I upvoted your answer. I don't have Intel SpeedStep® Technology on my system which explains how you have a 0000:04:00.0 where my PCI ends at 0000:03:00.0

            – WinEunuuchs2Unix
            Aug 10 at 4:03













            Quick correction, I had to enable it to remove the delay.

            – Omegastick
            Aug 10 at 4:12





            Quick correction, I had to enable it to remove the delay.

            – Omegastick
            Aug 10 at 4:12













            @Omegastick I did a quick edit. Changed "disabling" to "enabling"

            – WinEunuuchs2Unix
            Aug 10 at 14:59





            @Omegastick I did a quick edit. Changed "disabling" to "enabling"

            – WinEunuuchs2Unix
            Aug 10 at 14:59


















            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%2f1164632%2flong-kernel-load-time%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

            Tamil (spriik) Luke uk diar | Nawigatjuun

            Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

            Where does the image of a data connector as a sharp metal spike originate from?Where does the concept of infected people turning into zombies only after death originate from?Where does the motif of a reanimated human head originate?Where did the notion that Dragons could speak originate?Where does the archetypal image of the 'Grey' alien come from?Where did the suffix '-Man' originate?Where does the notion of being injured or killed by an illusion originate?Where did the term “sophont” originate?Where does the trope of magic spells being driven by advanced technology originate from?Where did the term “the living impaired” originate?