| 2016-12-05 08:41:58 |
Ying-Chun Liu |
bug |
|
|
added bug |
| 2016-12-05 08:41:58 |
Ying-Chun Liu |
attachment added |
|
Screenshot from 2016-11-30 02-08-01.png https://bugs.launchpad.net/bugs/1647283/+attachment/4787502/+files/Screenshot%20from%202016-11-30%2002-08-01.png |
|
| 2016-12-05 08:43:28 |
Ying-Chun Liu |
bug |
|
|
added subscriber Canonical Hardware Enablement Team |
| 2016-12-05 08:43:35 |
Ying-Chun Liu |
tags |
|
originate-from-1639117 somerville |
|
| 2016-12-05 08:52:52 |
Aron Xu |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=775613 |
|
| 2016-12-05 08:52:52 |
Aron Xu |
bug task added |
|
network-manager |
|
| 2016-12-05 09:12:28 |
Bug Watch Updater |
network-manager: status |
Unknown |
Confirmed |
|
| 2016-12-05 09:12:28 |
Bug Watch Updater |
network-manager: importance |
Unknown |
Medium |
|
| 2016-12-07 03:59:16 |
Chih-Hsyuan Ho |
bug task added |
|
oem-priority |
|
| 2016-12-07 04:00:30 |
Chih-Hsyuan Ho |
oem-priority: importance |
Undecided |
Critical |
|
| 2016-12-07 04:00:37 |
Chih-Hsyuan Ho |
oem-priority: milestone |
|
ubuntu12.04.4 |
|
| 2016-12-07 04:00:41 |
Chih-Hsyuan Ho |
oem-priority: milestone |
ubuntu12.04.4 |
|
|
| 2016-12-07 04:00:54 |
Chih-Hsyuan Ho |
bug |
|
|
added subscriber OEM Priority Team |
| 2016-12-07 04:01:04 |
Chih-Hsyuan Ho |
nominated for series |
|
oem-priority/xenial |
|
| 2016-12-07 04:01:04 |
Chih-Hsyuan Ho |
bug task added |
|
oem-priority/xenial |
|
| 2016-12-07 04:01:49 |
Chih-Hsyuan Ho |
bug |
|
|
added subscriber Chih-Hsyuan Ho |
| 2016-12-13 11:46:39 |
Bug Watch Updater |
network-manager: status |
Confirmed |
Fix Released |
|
| 2016-12-14 03:20:46 |
Kai-Heng Feng |
bug |
|
|
added subscriber Kai-Heng Feng |
| 2016-12-15 02:59:10 |
Kai-Heng Feng |
bug |
|
|
added subscriber Aron Xu |
| 2016-12-15 04:18:55 |
Anthony Wong |
network-manager (Ubuntu): assignee |
|
Aron Xu (happyaron) |
|
| 2016-12-20 11:57:57 |
Aron Xu |
network-manager (Ubuntu): importance |
Undecided |
High |
|
| 2016-12-20 11:57:57 |
Aron Xu |
network-manager (Ubuntu): status |
New |
Triaged |
|
| 2017-02-07 03:20:29 |
Cyrus Lien |
oem-priority: status |
New |
Triaged |
|
| 2017-02-07 03:20:45 |
Cyrus Lien |
oem-priority: assignee |
|
Alex Tu (alextu) |
|
| 2017-02-08 03:00:33 |
Alex Tu |
tags |
originate-from-1639117 somerville |
needed-by-1655901 originate-from-1639117 somerville |
|
| 2017-02-08 03:13:35 |
Yuan-Chen Cheng |
description |
Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613
Version: NetworkManager 1.4.2
This bug happens after power-on with probability about 1/50.
That means we need to reboot about 50 times to get into the buggy situation.
"nmcli d" shows the device type is ethernet:
DEVICE TYPE STATE CONNECTION
wlp1s0 ethernet unavailable --
lo loopback unmanaged --
The bug starts from a race condition. But it is not the root cause.
I've also attach 2 logs. One is in good situation. Another is in bad situation.
This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff.
In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is:
* During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
* Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
* Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type().
* Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared.
* And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0.
Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet.
But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet.
I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. |
Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613
Version: NetworkManager 1.4.2
This bug happens after power-on with probability about 1/50.
That means we need to reboot about 50 times to get into the buggy situation.
"nmcli d" shows the device type is ethernet:
DEVICE TYPE STATE CONNECTION
wlp1s0 ethernet unavailable --
lo loopback unmanaged --
The bug starts from a race condition. But it is not the root cause.
I've also attach 2 logs. One is in good situation. Another is in bad situation.
This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff.
In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is:
* During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
* Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
* Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type().
* Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared.
* And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0.
Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet.
But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet.
I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type.
fix need landing LP: #1645698 |
|
| 2017-02-16 17:07:49 |
Launchpad Janitor |
network-manager (Ubuntu): status |
Triaged |
Fix Released |
|
| 2017-03-06 04:16:22 |
Anthony Wong |
hwe-next: status |
New |
Fix Released |
|
| 2017-04-18 03:26:28 |
Alex Tu |
oem-priority: assignee |
Alex Tu (alextu) |
Shih-Yuan Lee (fourdollars) |
|
| 2017-04-18 03:33:28 |
Shih-Yuan Lee |
oem-priority: status |
Triaged |
Fix Released |
|
| 2017-04-18 03:33:30 |
Shih-Yuan Lee |
oem-priority/xenial: status |
New |
Fix Released |
|
| 2017-06-29 02:43:09 |
Shih-Yuan Lee |
oem-priority/xenial: status |
Fix Released |
New |
|
| 2017-06-29 02:43:20 |
Shih-Yuan Lee |
oem-priority: status |
Fix Released |
Confirmed |
|
| 2017-06-29 02:43:23 |
Shih-Yuan Lee |
oem-priority/xenial: status |
New |
Confirmed |
|
| 2017-07-07 03:55:18 |
Shih-Yuan Lee |
oem-priority: status |
Confirmed |
In Progress |
|
| 2017-07-07 03:55:21 |
Shih-Yuan Lee |
oem-priority/xenial: status |
Confirmed |
In Progress |
|
| 2017-07-07 04:13:11 |
Shih-Yuan Lee |
oem-priority/xenial: importance |
Undecided |
Critical |
|
| 2017-07-07 04:13:13 |
Shih-Yuan Lee |
oem-priority/xenial: assignee |
|
Shih-Yuan Lee (fourdollars) |
|
| 2017-07-14 10:14:21 |
Shih-Yuan Lee |
attachment added |
|
network-manager_1.2.6-0ubuntu0.16.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647283/+attachment/4914530/+files/network-manager_1.2.6-0ubuntu0.16.04.2.debdiff |
|
| 2017-07-14 10:37:51 |
Shih-Yuan Lee |
description |
Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613
Version: NetworkManager 1.4.2
This bug happens after power-on with probability about 1/50.
That means we need to reboot about 50 times to get into the buggy situation.
"nmcli d" shows the device type is ethernet:
DEVICE TYPE STATE CONNECTION
wlp1s0 ethernet unavailable --
lo loopback unmanaged --
The bug starts from a race condition. But it is not the root cause.
I've also attach 2 logs. One is in good situation. Another is in bad situation.
This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff.
In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is:
* During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
* Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
* Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type().
* Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared.
* And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0.
Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet.
But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet.
I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type.
fix need landing LP: #1645698 |
[Impact]
* It is a very bad user experience that the WiFi device is recognized as an Ethernet device making Ubuntu users unable to connect to WiFi network.
[Test Case]
* Find some laptop that can reduplicate this issue.
* Keep rebooting the system until you see this issue.
* Usually this issue can be reduplicated within 10 reboot cycles on the right laptop.
[Regression Potential]
* No trivial regression.
[Other Info]
* network-manager_1.2.6-0ubuntu0.16.04.2.debdiff (comment #8) is for xenial
[Original Bug Description]
Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613
Version: NetworkManager 1.4.2
This bug happens after power-on with probability about 1/50.
That means we need to reboot about 50 times to get into the buggy situation.
"nmcli d" shows the device type is ethernet:
DEVICE TYPE STATE CONNECTION
wlp1s0 ethernet unavailable --
lo loopback unmanaged --
The bug starts from a race condition. But it is not the root cause.
I've also attach 2 logs. One is in good situation. Another is in bad situation.
This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff.
In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is:
* During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
* Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
* Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type().
* Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared.
* And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0.
Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet.
But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet.
I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type.
fix need landing LP: #1645698 |
|
| 2017-07-14 10:38:06 |
Shih-Yuan Lee |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-07-14 10:58:28 |
Shih-Yuan Lee |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-07-14 11:05:23 |
Robie Basak |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-07-14 11:05:23 |
Robie Basak |
bug task added |
|
network-manager (Ubuntu Xenial) |
|
| 2017-07-14 16:55:34 |
Jeremy Bícha |
bug |
|
|
added subscriber Jeremy Bicha |
| 2017-09-06 05:45:06 |
Yuan-Chen Cheng |
oem-priority: importance |
Critical |
High |
|
| 2017-12-20 02:19:43 |
Yuan-Chen Cheng |
oem-priority/xenial: status |
In Progress |
Confirmed |
|
| 2017-12-20 02:21:00 |
Yuan-Chen Cheng |
oem-priority/xenial: importance |
Critical |
Medium |
|
| 2020-08-15 17:18:34 |
Rex Tsai |
tags |
needed-by-1655901 originate-from-1639117 somerville |
needed-by-1655901 oem-priority originate-from-1639117 somerville |
|
