dbus daemon spinning with NM AP properties change event
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Unassigned | ||
location-service (Ubuntu RTM) |
Fix Released
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
network-manager (Ubuntu RTM) |
Invalid
|
Critical
|
Unassigned |
Bug Description
I am consistently seeing this in the Bluefin office this week
Mako running 133
Phone gets warm in pocket, wake up the phone and attach
top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20%
It never quiets own, at least not for over 5 mins
3g data is turned off
Cellular is roaming to local carrier fwiw
Seems to happen whenever I leave the AP coverage, whether I return or not
Reproducing the issue: The problem is easily reproducible when forcing NM to roam between multiple access points and never quite finishing the association to one AP. At home, I reproduce by
roaming between different floors, where each floor has got its own WiFi. Any sufficiently complex office WiFi setup should trigger it, too.
Related branches
- Loïc Minier: Approve
- PS Jenkins bot: Needs Fixing (continuous-integration)
-
Diff: 80 lines (+11/-31)2 files modifiedsrc/location_service/com/ubuntu/location/connectivity/ofono.h (+7/-4)
src/location_service/com/ubuntu/location/connectivity/ofono_nm_connectivity_manager.cpp (+4/-27)
Changed in network-manager (Ubuntu RTM): | |
importance: | Undecided → Critical |
assignee: | nobody → Ricardo Mendoza (ricmm) |
Changed in location-service: | |
importance: | Undecided → Critical |
assignee: | nobody → Thomas Voß (thomas-voss) |
description: | updated |
description: | updated |
Changed in canonical-devices-system-image: | |
milestone: | ww51-2014 → ww03-2015 |
Changed in location-service: | |
status: | New → In Progress |
Changed in location-service (Ubuntu RTM): | |
status: | New → In Progress |
no longer affects: | location-service |
I see lots of these messages:
Nov 19 08:03:43 ubuntu-phablet NetworkManager[ 1448]: <warn> Activation (wlan0/wireless): association took too long, failing activation. 1448]: <info> (wlan0): device state change: config -> failed (reason 'SSID not found') [50 120 53] 1448]: <info> NetworkManager state is now DISCONNECTED 1448]: <warn> Activation (wlan0) failed for connection 'Canonical-5GHz-an' 1448]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0] 1448]: <info> (wlan0): deactivating device (reason 'none') [0] ResultsToMainLi st: 2908: 11d AP Bssid 84:18:3a:44:da:ec chan= 36, rssi = -50, countryCode US ResultsToMainLi st: 2908: 11d AP Bssid 84:18:3a:44:da:e8 chan= 8, rssi = -40, countryCode US ResultsToMainLi st: 2928: Information about current country Bssid 84:18:3a:04:da:e8 chan= 8, rssi = -40, countryCode US 1828]: wlan0: Failed to initiate sched scan 1828]: wlan0: CTRL-EVENT- SCAN-STARTED ResultsToMainLi st: 2908: 11d AP Bssid 84:18:3a:08:65:b8 chan= 4, rssi = -84, countryCode US ResultsToMainLi st: 2908: 11d AP Bssid 84:18:3a:44:da:ec chan= 36, rssi = -50, countryCode US ResultsToMainLi st: 2908: 11d AP Bssid 84:18:3a:44:da:e8 chan= 8, rssi = -38, countryCode US ResultsToMainLi st: 2908: 11d AP Bssid 84:18:3a:04:da:e8 chan= 8, rssi = -37, countryCode US ResultsToMainLi st: 2928: Information about current country Bssid 84:18:3a:04:da:e8 chan= 8, rssi = -37, countryCode US 1448]: <info> (wlan0): supplicant interface state: scanning -> disconnected 1448]: <warn> Couldn't disconnect supplicant interface: This interface is not connected
Nov 19 08:03:43 ubuntu-phablet NetworkManager[
Nov 19 08:03:43 ubuntu-phablet NetworkManager[
Nov 19 08:03:43 ubuntu-phablet NetworkManager[
Nov 19 08:03:43 ubuntu-phablet NetworkManager[
Nov 19 08:03:43 ubuntu-phablet NetworkManager[
Nov 19 08:03:43 ubuntu-phablet kernel: [51481.120852] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:43 ubuntu-phablet kernel: [51481.121920] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:43 ubuntu-phablet kernel: [51481.122835] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:43 ubuntu-phablet wpa_supplicant[
Nov 19 08:03:43 ubuntu-phablet wpa_supplicant[
Nov 19 08:03:44 ubuntu-phablet kernel: [51482.020195] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:44 ubuntu-phablet kernel: [51482.021142] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:44 ubuntu-phablet kernel: [51482.021935] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:44 ubuntu-phablet kernel: [51482.022912] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:44 ubuntu-phablet kernel: [51482.023614] wlan: [1317:E :SME] csrMoveTempScan
Nov 19 08:03:45 ubuntu-phablet NetworkManager[
Nov 19 08:03:45 ubuntu-phablet NetworkManager[
It tells me you're likely just outside of the range of the accesspoints, and since it comes in and out of scan results regularly, NM will keep trying to authenticate while the AP is available.
A couple of things to try:
- Switch to 2.4GHz, see if the behavior is the same, this could give us some interesting data points.
- Disable location, which causes significantly more wifi scans to be triggered, and reducing that may also improve the situation.
- Try to attach strace to...