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 :/
networking drivers intel-wireless iwlwifi
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.
add a comment |
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 :/
networking drivers intel-wireless iwlwifi
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 iwlAs 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 fromdmesg | grep iwlpaste.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
add a comment |
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 :/
networking drivers intel-wireless iwlwifi
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
networking drivers intel-wireless iwlwifi
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.
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 iwlAs 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 fromdmesg | grep iwlpaste.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
add a comment |
Please run after the wireless is stuck:dmesg | grep iwlAs 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 fromdmesg | grep iwlpaste.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
add a comment |
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.
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered 23 hours ago
chili555
37.5k54976
37.5k54976
add a comment |
add a comment |
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.
sleipnir is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Please run after the wireless is stuck:
dmesg | grep iwlAs 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 iwlpaste.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