mwifiex_pcie crashes after several bind/unbind
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Jesse Sung | ||
linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Xenial |
Won't Fix
|
Undecided
|
Unassigned | ||
Yakkety |
Won't Fix
|
Undecided
|
Unassigned | ||
nplan (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
netplan-configured systems with mwifiex interfaces crash if netplan attempts to unbind/bind the interface.
[Test case]
1) Run 'netplan apply' on a system with mwifiex_pci driver.
The system should not crash, and the mwifiex interface should remain untouched.
[Regression potential]
Interfaces other than those affected by unbind/bind crashes or failures should still be unbound when 'netplan apply' is run. This affects most wireless interfaces, with the notable exception of mwifiex and brcmfmac. Failure to apply netplan configuration for a legitimate mwifiex device (wireless connection driven by NetworkManager renderer using netplan) would also constitute a regression.
[Original bug report]
# echo 0000:03:00.0 > /sys/bus/
# echo 0000:03:00.0 > /sys/bus/
Keep doing the bind/unbind actions, it would crash very soon.
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
tags: | added: kernel-da-key |
Changed in hwe-next: | |
assignee: | nobody → Jesse Sung (wenchien) |
description: | updated |
Changed in nplan (Ubuntu Xenial): | |
status: | Fix Committed → Fix Released |
tags: | added: cscc |
Changed in hwe-next: | |
status: | New → Fix Released |
Changed in linux (Ubuntu Xenial): | |
status: | New → Won't Fix |
Changed in linux (Ubuntu): | |
status: | Triaged → Invalid |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1630285
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.