| 2018-01-15 02:31:41 |
Andre Brait |
bug |
|
|
added bug |
| 2018-01-15 03:42:07 |
Andre Brait |
description |
After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work.
After googling a lot, I came across this question on askubuntu.com
https://askubuntu.com/questions/967355/wifi-unstable-after-17-10-update
While led me to this bug report on Debian's bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184
Which led me to this bug in upstream:
http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html
I've tested the proposed fixes myself and I can confirm they work.
What causes the WiFi to stop working is a bug related to the group rekeying routines. Updating the board-2.bin and firmware-6.bin from kvalo's git repository for version RM4.4.1 has worked for me and for other users as well.
It seems it only happend in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3.
The files were fetched from https://github.com/kvalo/ath10k-firmware as of this date, as of commit 35d8642f452827b955470de4ac997ffe906a6f17, with the following sha256 sums:
8fcc6b96c1895bc227c3caf0bd04b23d0292f8f919e819e4e025e29ef4b44d8e board-2.bin
30fc3db3af9ba9f3b88e523fe39b715826a31738d48ca01a3fad0d14f7e46e20 firmware-6.bin_WLAN.RM.4.4.1-00065-QCARMSWP-1
It seems firmware-6.bin_WLAN.RM.4.4.1-00079-QCARMSWPZ-1 (sha256sum 5554d6aa0de07394938a0094bae725ed24d4ceee3b38c849b4099a496ec50b48) works as well.
-------------------------------------------------------------
Description: Ubuntu 16.04.3 LTS
Release: 16.04
linux-firmware:
Instalado: 1.157.14
Candidato: 1.157.14
Tabela de versão:
*** 1.157.14 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
1.157 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages |
After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work.
After googling a lot, I came across this question on askubuntu.com
https://askubuntu.com/questions/967355/wifi-unstable-after-17-10-update
Which led me to this bug report on Debian's bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184
Which led me to this bug in upstream:
http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html
I've tested the proposed fixes myself and I can confirm they work.
What causes the WiFi to stop working is a bug related to the group rekeying routines.
It seems it only happens in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3.
kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1 of the firmware-6.bin file, which is the current one present in upstream.
Updating the firmware-6.bin and board-2.bin to any version equal or later than that fixes the issue completely.
-------------------------------------------------------------
SRU Justification:
[Impact]
Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred.
Additionally, this happens for the only HWE kernel that's been patched against the recent Meltdown vulnerability, leaving the user without the option of using a recent kernel and a secure kernel at the same time.
[Test Case]
After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with
$ cat /var/log/syslog | grep wpa_.*rekeying
[Regression Potential]
The new firmware overwrites the old one, but since it's been in upstream since October 2017, it should be good.
-------------------------------------------------------------
Description: Ubuntu 16.04.3 LTS
Release: 16.04
linux-firmware:
Instalado: 1.157.14
Candidato: 1.157.14
Tabela de versão:
*** 1.157.14 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
1.157 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages |
|
| 2018-01-15 19:48:15 |
Launchpad Janitor |
linux-firmware (Ubuntu): status |
New |
Confirmed |
|
| 2018-01-15 23:44:07 |
Hector |
bug |
|
|
added subscriber Hector |
| 2018-01-16 11:12:34 |
WinEunuchs2Unix |
bug |
|
|
added subscriber WinEunuchs2Unix |
| 2018-01-16 17:26:56 |
Andre Brait |
description |
After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work.
After googling a lot, I came across this question on askubuntu.com
https://askubuntu.com/questions/967355/wifi-unstable-after-17-10-update
Which led me to this bug report on Debian's bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184
Which led me to this bug in upstream:
http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html
I've tested the proposed fixes myself and I can confirm they work.
What causes the WiFi to stop working is a bug related to the group rekeying routines.
It seems it only happens in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3.
kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1 of the firmware-6.bin file, which is the current one present in upstream.
Updating the firmware-6.bin and board-2.bin to any version equal or later than that fixes the issue completely.
-------------------------------------------------------------
SRU Justification:
[Impact]
Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred.
Additionally, this happens for the only HWE kernel that's been patched against the recent Meltdown vulnerability, leaving the user without the option of using a recent kernel and a secure kernel at the same time.
[Test Case]
After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with
$ cat /var/log/syslog | grep wpa_.*rekeying
[Regression Potential]
The new firmware overwrites the old one, but since it's been in upstream since October 2017, it should be good.
-------------------------------------------------------------
Description: Ubuntu 16.04.3 LTS
Release: 16.04
linux-firmware:
Instalado: 1.157.14
Candidato: 1.157.14
Tabela de versão:
*** 1.157.14 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
1.157 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages |
After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work.
After googling a lot, I came across this question on askubuntu.com
https://askubuntu.com/questions/967355/wifi-unstable-after-17-10-update
Which led me to this bug report on Debian's bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184
Which led me to this bug in upstream:
http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html
I've tested the proposed fixes myself and I can confirm they work.
What causes the WiFi to stop working is a bug related to the group rekeying routines.
It seems it only happens in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3.
kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1 of the firmware-6.bin file, which is the current one present in upstream.
Updating the firmware-6.bin (and board-2.bin, optionally) to any version equal or later than that fixes the issue completely.
-------------------------------------------------------------
SRU Justification:
[Impact]
Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred.
Additionally, this happens for the only HWE kernel that's been patched against the recent Meltdown vulnerability, leaving the user without the option of using a recent kernel and a secure kernel at the same time.
[Test Case]
After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with
$ cat /var/log/syslog | grep wpa_.*rekeying
[How to fix it]
Update the firmware-6.bin file to version WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.
[Regression Potential]
The new firmware overwrites the old one, but since it's been in upstream since October 2017, it should be good.
-------------------------------------------------------------
Description: Ubuntu 16.04.3 LTS
Release: 16.04
linux-firmware:
Instalado: 1.157.14
Candidato: 1.157.14
Tabela de versão:
*** 1.157.14 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
1.157 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages |
|
| 2018-01-17 14:22:23 |
Andre Brait |
bug |
|
|
added subscriber AceLan Kao |
| 2018-01-17 16:01:49 |
Seth Forshee |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-01-17 16:01:49 |
Seth Forshee |
bug task added |
|
linux-firmware (Ubuntu Xenial) |
|
| 2018-01-17 16:01:56 |
Seth Forshee |
linux-firmware (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2018-01-17 16:02:07 |
Seth Forshee |
linux-firmware (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2018-01-17 16:02:07 |
Seth Forshee |
linux-firmware (Ubuntu Xenial): status |
New |
In Progress |
|
| 2018-01-17 16:02:07 |
Seth Forshee |
linux-firmware (Ubuntu Xenial): assignee |
|
Seth Forshee (sforshee) |
|
| 2018-01-17 16:06:37 |
Seth Forshee |
linux-firmware (Ubuntu Xenial): status |
In Progress |
Incomplete |
|
| 2018-01-18 14:20:41 |
Seth Forshee |
linux-firmware (Ubuntu Xenial): status |
Incomplete |
Fix Committed |
|
| 2018-01-19 13:29:24 |
Seth Forshee |
nominated for series |
|
Ubuntu Artful |
|
| 2018-01-19 13:29:24 |
Seth Forshee |
bug task added |
|
linux-firmware (Ubuntu Artful) |
|
| 2018-01-23 17:17:07 |
Launchpad Janitor |
linux-firmware (Ubuntu Artful): status |
New |
Confirmed |
|
| 2018-01-24 10:39:51 |
Stephan Eckweiler |
bug |
|
|
added subscriber Stephan Eckweiler |
| 2018-01-24 15:28:18 |
Seth Forshee |
linux-firmware (Ubuntu Artful): importance |
Undecided |
Medium |
|
| 2018-01-24 15:28:18 |
Seth Forshee |
linux-firmware (Ubuntu Artful): status |
Confirmed |
Fix Committed |
|
| 2018-01-24 15:28:18 |
Seth Forshee |
linux-firmware (Ubuntu Artful): assignee |
|
Seth Forshee (sforshee) |
|
| 2018-01-26 09:47:18 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-01-26 09:47:20 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-01-26 18:48:05 |
Eugene Savelov |
bug |
|
|
added subscriber Eugene Savelov |
| 2018-01-28 23:15:30 |
Bruce |
bug |
|
|
added subscriber Bruce Steedman |
| 2018-01-30 01:22:42 |
Andre Brait |
tags |
ath10k qca6174 rekeying |
ath10k qca6174 rekeying verification-done-xenial |
|
| 2018-01-30 01:23:30 |
Andre Brait |
tags |
ath10k qca6174 rekeying verification-done-xenial |
ath10k qca6174 rekeying verification-done-xenial verification-needed-artful |
|
| 2018-01-30 15:14:39 |
Andre Brait |
tags |
ath10k qca6174 rekeying verification-done-xenial verification-needed-artful |
ath10k qca6174 rekeying verification-done-artful verification-done-xenial |
|
| 2018-01-31 06:10:38 |
petr |
bug |
|
|
added subscriber petr |
| 2018-02-05 08:43:31 |
Launchpad Janitor |
linux-firmware (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2018-02-05 08:43:34 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-02-14 14:20:50 |
Launchpad Janitor |
linux-firmware (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-08-01 07:38:47 |
Tugkan Batu |
bug |
|
|
added subscriber Tugkan Batu |
| 2019-04-28 22:23:27 |
Pablo A. Garcia |
bug |
|
|
added subscriber Pablo A. Garcia |
