Queue 10 is active on fifo 2 and stuck for 10000 ms











up vote
0
down vote

favorite












I've installed Ubuntu 18.04 LTS a few days and started having issues with the wifi adapter (intel dual band wireless ac-3160), where it would randomly stop working after some point of time (sometimes immediately after boot, sometimes hours after startup) and required a restart before it would work again. Looking through dmesg for clues as to what is going on, I saw



Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [3, 19] HW [90, 90] FH TRB=0x05a5a5a5a


I'm not sure what's going on here but I've done some searching online and among the solutions i found (turn off power management, use an older kernel, update firmware, disable bluetooth, etc) none of them seem to work. I really want to keep using Ubuntu since it's so much more convenient to complete schoolwork with it rather than Windows but if I cannot fix this intermittent issue then I will have to go back to Windows :/










share|improve this question







New contributor




sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Please run after the wireless is stuck: dmesg | grep iwl As the result will be lengthy, paste the result here and give us the link: paste.ubuntu.com Welcome to Ask Ubuntu.
    – chili555
    2 days ago










  • @chili555 Hi there, Here's the output from dmesg | grep iwl paste.ubuntu.com/p/3bhzQVXYSW it seems to be happening on/right after bootup now.
    – sleipnir
    yesterday










  • Is this a dual boot with Windows? Does the device work as expected in Windows? Is there any difference between a cold boot and a reboot?
    – chili555
    yesterday










  • It's not a dual boot, only Ubuntu right now. The device did work previously under Windows. No difference between reboot and cold bootup...
    – sleipnir
    yesterday















up vote
0
down vote

favorite












I've installed Ubuntu 18.04 LTS a few days and started having issues with the wifi adapter (intel dual band wireless ac-3160), where it would randomly stop working after some point of time (sometimes immediately after boot, sometimes hours after startup) and required a restart before it would work again. Looking through dmesg for clues as to what is going on, I saw



Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [3, 19] HW [90, 90] FH TRB=0x05a5a5a5a


I'm not sure what's going on here but I've done some searching online and among the solutions i found (turn off power management, use an older kernel, update firmware, disable bluetooth, etc) none of them seem to work. I really want to keep using Ubuntu since it's so much more convenient to complete schoolwork with it rather than Windows but if I cannot fix this intermittent issue then I will have to go back to Windows :/










share|improve this question







New contributor




sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Please run after the wireless is stuck: dmesg | grep iwl As the result will be lengthy, paste the result here and give us the link: paste.ubuntu.com Welcome to Ask Ubuntu.
    – chili555
    2 days ago










  • @chili555 Hi there, Here's the output from dmesg | grep iwl paste.ubuntu.com/p/3bhzQVXYSW it seems to be happening on/right after bootup now.
    – sleipnir
    yesterday










  • Is this a dual boot with Windows? Does the device work as expected in Windows? Is there any difference between a cold boot and a reboot?
    – chili555
    yesterday










  • It's not a dual boot, only Ubuntu right now. The device did work previously under Windows. No difference between reboot and cold bootup...
    – sleipnir
    yesterday













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I've installed Ubuntu 18.04 LTS a few days and started having issues with the wifi adapter (intel dual band wireless ac-3160), where it would randomly stop working after some point of time (sometimes immediately after boot, sometimes hours after startup) and required a restart before it would work again. Looking through dmesg for clues as to what is going on, I saw



Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [3, 19] HW [90, 90] FH TRB=0x05a5a5a5a


I'm not sure what's going on here but I've done some searching online and among the solutions i found (turn off power management, use an older kernel, update firmware, disable bluetooth, etc) none of them seem to work. I really want to keep using Ubuntu since it's so much more convenient to complete schoolwork with it rather than Windows but if I cannot fix this intermittent issue then I will have to go back to Windows :/










share|improve this question







New contributor




sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I've installed Ubuntu 18.04 LTS a few days and started having issues with the wifi adapter (intel dual band wireless ac-3160), where it would randomly stop working after some point of time (sometimes immediately after boot, sometimes hours after startup) and required a restart before it would work again. Looking through dmesg for clues as to what is going on, I saw



Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [3, 19] HW [90, 90] FH TRB=0x05a5a5a5a


I'm not sure what's going on here but I've done some searching online and among the solutions i found (turn off power management, use an older kernel, update firmware, disable bluetooth, etc) none of them seem to work. I really want to keep using Ubuntu since it's so much more convenient to complete schoolwork with it rather than Windows but if I cannot fix this intermittent issue then I will have to go back to Windows :/







networking drivers intel-wireless iwlwifi






share|improve this question







New contributor




sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









sleipnir

1




1




New contributor




sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






sleipnir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • Please run after the wireless is stuck: dmesg | grep iwl As the result will be lengthy, paste the result here and give us the link: paste.ubuntu.com Welcome to Ask Ubuntu.
    – chili555
    2 days ago










  • @chili555 Hi there, Here's the output from dmesg | grep iwl paste.ubuntu.com/p/3bhzQVXYSW it seems to be happening on/right after bootup now.
    – sleipnir
    yesterday










  • Is this a dual boot with Windows? Does the device work as expected in Windows? Is there any difference between a cold boot and a reboot?
    – chili555
    yesterday










  • It's not a dual boot, only Ubuntu right now. The device did work previously under Windows. No difference between reboot and cold bootup...
    – sleipnir
    yesterday


















  • Please run after the wireless is stuck: dmesg | grep iwl As the result will be lengthy, paste the result here and give us the link: paste.ubuntu.com Welcome to Ask Ubuntu.
    – chili555
    2 days ago










  • @chili555 Hi there, Here's the output from dmesg | grep iwl paste.ubuntu.com/p/3bhzQVXYSW it seems to be happening on/right after bootup now.
    – sleipnir
    yesterday










  • Is this a dual boot with Windows? Does the device work as expected in Windows? Is there any difference between a cold boot and a reboot?
    – chili555
    yesterday










  • It's not a dual boot, only Ubuntu right now. The device did work previously under Windows. No difference between reboot and cold bootup...
    – sleipnir
    yesterday
















Please run after the wireless is stuck: dmesg | grep iwl As the result will be lengthy, paste the result here and give us the link: paste.ubuntu.com Welcome to Ask Ubuntu.
– chili555
2 days ago




Please run after the wireless is stuck: dmesg | grep iwl As the result will be lengthy, paste the result here and give us the link: paste.ubuntu.com Welcome to Ask Ubuntu.
– chili555
2 days ago












@chili555 Hi there, Here's the output from dmesg | grep iwl paste.ubuntu.com/p/3bhzQVXYSW it seems to be happening on/right after bootup now.
– sleipnir
yesterday




@chili555 Hi there, Here's the output from dmesg | grep iwl paste.ubuntu.com/p/3bhzQVXYSW it seems to be happening on/right after bootup now.
– sleipnir
yesterday












Is this a dual boot with Windows? Does the device work as expected in Windows? Is there any difference between a cold boot and a reboot?
– chili555
yesterday




Is this a dual boot with Windows? Does the device work as expected in Windows? Is there any difference between a cold boot and a reboot?
– chili555
yesterday












It's not a dual boot, only Ubuntu right now. The device did work previously under Windows. No difference between reboot and cold bootup...
– sleipnir
yesterday




It's not a dual boot, only Ubuntu right now. The device did work previously under Windows. No difference between reboot and cold bootup...
– sleipnir
yesterday










1 Answer
1






active

oldest

votes

















up vote
0
down vote













In your dmesg, we see these alarming lines:



[   47.424641] iwlwifi 0000:03:00.0: Failed to wake NIC for hcmd
[ 47.424688] iwlwifi 0000:03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
[ 47.424694] iwlwifi 0000:03:00.0: Scan failed! ret -5
[ 48.109479] iwlwifi 0000:03:00.0: iwlwifi transaction failed, dumping registers


A search suggests a possible fix. Reference: https://bbs.archlinux.org/viewtopic.php?id=240916




try "net.ipv4.tcp_ecn=0" (either a kernel parameter or via sysctl)




Let’s add this as a boot parameter and see if performance improves. From the terminal:



sudo nano /etc/default/grub


Find this line:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


Change it to this:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash net.ipv4.tcp_ecn=0"


Save (Ctrl+o followed by Enter) and exit nano (Ctrl+x).



Now do:



sudo update grub


Reboot and paste, as above:



dmesg | grep iwl


And give us the link.






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',
    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
    });


    }
    });






    sleipnir is a new contributor. Be nice, and check out our Code of Conduct.










     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093852%2fqueue-10-is-active-on-fifo-2-and-stuck-for-10000-ms%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








    up vote
    0
    down vote













    In your dmesg, we see these alarming lines:



    [   47.424641] iwlwifi 0000:03:00.0: Failed to wake NIC for hcmd
    [ 47.424688] iwlwifi 0000:03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
    [ 47.424694] iwlwifi 0000:03:00.0: Scan failed! ret -5
    [ 48.109479] iwlwifi 0000:03:00.0: iwlwifi transaction failed, dumping registers


    A search suggests a possible fix. Reference: https://bbs.archlinux.org/viewtopic.php?id=240916




    try "net.ipv4.tcp_ecn=0" (either a kernel parameter or via sysctl)




    Let’s add this as a boot parameter and see if performance improves. From the terminal:



    sudo nano /etc/default/grub


    Find this line:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


    Change it to this:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash net.ipv4.tcp_ecn=0"


    Save (Ctrl+o followed by Enter) and exit nano (Ctrl+x).



    Now do:



    sudo update grub


    Reboot and paste, as above:



    dmesg | grep iwl


    And give us the link.






    share|improve this answer

























      up vote
      0
      down vote













      In your dmesg, we see these alarming lines:



      [   47.424641] iwlwifi 0000:03:00.0: Failed to wake NIC for hcmd
      [ 47.424688] iwlwifi 0000:03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
      [ 47.424694] iwlwifi 0000:03:00.0: Scan failed! ret -5
      [ 48.109479] iwlwifi 0000:03:00.0: iwlwifi transaction failed, dumping registers


      A search suggests a possible fix. Reference: https://bbs.archlinux.org/viewtopic.php?id=240916




      try "net.ipv4.tcp_ecn=0" (either a kernel parameter or via sysctl)




      Let’s add this as a boot parameter and see if performance improves. From the terminal:



      sudo nano /etc/default/grub


      Find this line:



      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


      Change it to this:



      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash net.ipv4.tcp_ecn=0"


      Save (Ctrl+o followed by Enter) and exit nano (Ctrl+x).



      Now do:



      sudo update grub


      Reboot and paste, as above:



      dmesg | grep iwl


      And give us the link.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        In your dmesg, we see these alarming lines:



        [   47.424641] iwlwifi 0000:03:00.0: Failed to wake NIC for hcmd
        [ 47.424688] iwlwifi 0000:03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
        [ 47.424694] iwlwifi 0000:03:00.0: Scan failed! ret -5
        [ 48.109479] iwlwifi 0000:03:00.0: iwlwifi transaction failed, dumping registers


        A search suggests a possible fix. Reference: https://bbs.archlinux.org/viewtopic.php?id=240916




        try "net.ipv4.tcp_ecn=0" (either a kernel parameter or via sysctl)




        Let’s add this as a boot parameter and see if performance improves. From the terminal:



        sudo nano /etc/default/grub


        Find this line:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


        Change it to this:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash net.ipv4.tcp_ecn=0"


        Save (Ctrl+o followed by Enter) and exit nano (Ctrl+x).



        Now do:



        sudo update grub


        Reboot and paste, as above:



        dmesg | grep iwl


        And give us the link.






        share|improve this answer












        In your dmesg, we see these alarming lines:



        [   47.424641] iwlwifi 0000:03:00.0: Failed to wake NIC for hcmd
        [ 47.424688] iwlwifi 0000:03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
        [ 47.424694] iwlwifi 0000:03:00.0: Scan failed! ret -5
        [ 48.109479] iwlwifi 0000:03:00.0: iwlwifi transaction failed, dumping registers


        A search suggests a possible fix. Reference: https://bbs.archlinux.org/viewtopic.php?id=240916




        try "net.ipv4.tcp_ecn=0" (either a kernel parameter or via sysctl)




        Let’s add this as a boot parameter and see if performance improves. From the terminal:



        sudo nano /etc/default/grub


        Find this line:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


        Change it to this:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash net.ipv4.tcp_ecn=0"


        Save (Ctrl+o followed by Enter) and exit nano (Ctrl+x).



        Now do:



        sudo update grub


        Reboot and paste, as above:



        dmesg | grep iwl


        And give us the link.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 23 hours ago









        chili555

        37.5k54976




        37.5k54976






















            sleipnir is a new contributor. Be nice, and check out our Code of Conduct.










             

            draft saved


            draft discarded


















            sleipnir is a new contributor. Be nice, and check out our Code of Conduct.













            sleipnir is a new contributor. Be nice, and check out our Code of Conduct.












            sleipnir is a new contributor. Be nice, and check out our Code of Conduct.















             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093852%2fqueue-10-is-active-on-fifo-2-and-stuck-for-10000-ms%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

            Mouse cursor on multiple screens with different PPI

            Agildo Ribeiro

            Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”