| 2020-08-14 10:46:38 |
Leon Liao |
bug |
|
|
added bug |
| 2020-08-14 10:48:08 |
Leon Liao |
information type |
Proprietary |
Public |
|
| 2020-08-14 10:49:31 |
Leon Liao |
bug task added |
|
network-manager (Ubuntu) |
|
| 2020-08-14 10:49:43 |
Leon Liao |
oem-priority: assignee |
|
Leon Liao (lihow731) |
|
| 2020-08-14 10:51:41 |
Leon Liao |
merge proposal linked |
|
https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865 |
|
| 2020-08-14 11:30:43 |
Leon Liao |
description |
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager. |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi functiall still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* No potential regressions.
[Other Info]
* None |
|
| 2020-08-15 16:48:08 |
Rex Tsai |
tags |
|
oem-priority |
|
| 2020-08-25 07:31:50 |
Leon Liao |
nominated for series |
|
oem-priority/focal |
|
| 2020-08-25 07:31:50 |
Leon Liao |
bug task added |
|
oem-priority/focal |
|
| 2020-08-25 07:32:03 |
Leon Liao |
bug task deleted |
oem-priority/focal |
|
|
| 2020-08-25 08:34:49 |
Leon Liao |
attachment added |
|
network-manager_1.22.10-1ubuntu2.2.debdiff https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891632/+attachment/5404329/+files/network-manager_1.22.10-1ubuntu2.2.debdiff |
|
| 2020-08-25 12:28:31 |
Ubuntu Foundations Team Bug Bot |
tags |
oem-priority |
oem-priority patch |
|
| 2020-08-25 12:28:38 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2020-09-16 09:48:04 |
Leon Liao |
merge proposal linked |
|
https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/390544 |
|
| 2020-09-16 09:50:39 |
Leon Liao |
merge proposal unlinked |
https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865 |
|
|
| 2020-09-16 16:03:36 |
Iain Lane |
nominated for series |
|
oem-priority/focal |
|
| 2020-09-16 16:03:36 |
Iain Lane |
bug task added |
|
oem-priority/focal |
|
| 2020-09-16 16:03:52 |
Iain Lane |
oem-priority/focal: status |
New |
Invalid |
|
| 2020-09-16 16:04:07 |
Iain Lane |
nominated for series |
|
Ubuntu Focal |
|
| 2020-09-16 16:04:07 |
Iain Lane |
bug task added |
|
network-manager (Ubuntu Focal) |
|
| 2020-09-16 16:04:16 |
Iain Lane |
network-manager (Ubuntu): status |
New |
Fix Released |
|
| 2020-09-16 16:04:19 |
Iain Lane |
network-manager (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-09-16 16:04:26 |
Iain Lane |
network-manager (Ubuntu Focal): assignee |
|
Leon Liao (lihow731) |
|
| 2020-09-17 10:05:31 |
Tiffany |
bug |
|
|
added subscriber Tiffany |
| 2020-09-23 12:16:10 |
Robie Basak |
network-manager (Ubuntu Focal): status |
In Progress |
Incomplete |
|
| 2020-09-24 14:24:05 |
Sebastien Bacher |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2020-09-25 03:27:10 |
Leon Liao |
description |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi functiall still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* No potential regressions.
[Other Info]
* None |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi functiall still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network won't management the WOW forever.
[Other Info]
* None |
|
| 2020-09-25 03:29:00 |
Leon Liao |
description |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi functiall still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network won't management the WOW forever.
[Other Info]
* None |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi functiall still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network won't management the WOW function forever. The WOW function totally depend on device driver.
[Other Info]
* None |
|
| 2020-09-25 10:18:47 |
Leon Liao |
description |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi functiall still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network won't management the WOW function forever. The WOW function totally depend on device driver.
[Other Info]
* None |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi function still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values.
[Other Info]
* None |
|
| 2020-09-28 03:06:59 |
Leon Liao |
network-manager (Ubuntu Focal): status |
Incomplete |
In Progress |
|
| 2020-09-29 16:37:46 |
Brian Murray |
network-manager (Ubuntu Focal): status |
In Progress |
Incomplete |
|
| 2020-10-27 06:26:58 |
Leon Liao |
description |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi function still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values.
[Other Info]
* None |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi function still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values.
1. Magic packet test:
Set Wake on Wireless to off
Send magic packet to the system
Ensure it does not wake up
Set Wake on Wirless to on
Send magic packet to the system
Ensure it does wake up
2. Wi-Fi function test after resumed from suspend:
After resume from suspend, the Wi-Fi should work normally.
Scan APs.
Connect to an AP.
[Other Info]
* None |
|
| 2020-10-27 06:27:05 |
Leon Liao |
network-manager (Ubuntu Focal): status |
Incomplete |
In Progress |
|
| 2020-10-27 14:49:46 |
Rex Tsai |
description |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi function still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values.
1. Magic packet test:
Set Wake on Wireless to off
Send magic packet to the system
Ensure it does not wake up
Set Wake on Wirless to on
Send magic packet to the system
Ensure it does wake up
2. Wi-Fi function test after resumed from suspend:
After resume from suspend, the Wi-Fi should work normally.
Scan APs.
Connect to an AP.
[Other Info]
* None |
[Impact]
In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit.
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
So, the management of wake-on-LAN still is done by NetworkManager.
The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend.
[Test Case]
On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
Step 1. Enter suspend (s2idle)
Setp 2. Resume from suspend
After resume from suspend, the Wi-Fi function still is normal.
You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
[Regression Potential]
* This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values.
1. Magic packet test:
Set Wake on Wireless to off
Send magic packet to the system
Ensure it does not wake up
Set Wake on Wirless to on
Send magic packet to the system
Ensure it does wake up
2. Wi-Fi function test after resumed from suspend:
After resume from suspend, the Wi-Fi should work normally.
Scan APs.
Connect to an AP.
[Other Info]
* platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status check (!597) · Merge Requests · NetworkManager / NetworkManager · GitLab - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639 |
|
| 2020-10-28 03:55:16 |
Rex Tsai |
bug |
|
|
added subscriber Rex Tsai |
| 2020-11-03 22:04:50 |
Brian Murray |
network-manager (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-11-03 22:04:52 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-11-03 22:04:56 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2020-11-03 22:05:00 |
Brian Murray |
tags |
oem-priority patch |
oem-priority patch verification-needed verification-needed-focal |
|
| 2020-11-04 08:19:51 |
You-Sheng Yang |
tags |
oem-priority patch verification-needed verification-needed-focal |
oem-priority patch verification-done verification-done-focal |
|
| 2020-11-12 11:15:28 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-11-12 11:15:26 |
Launchpad Janitor |
network-manager (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-12-11 02:54:20 |
Leon Liao |
oem-priority: status |
New |
Fix Committed |
|
| 2020-12-11 02:54:24 |
Leon Liao |
oem-priority: status |
Fix Committed |
Fix Released |
|
