desktop-packages team mailing list archive

[Thomas Voß <1394204@xxxxxxxxxxxxxxxxxx>]

I tracked down the root cause to the location service reacting to
changes to the "PrimaryConnection" property of
org.freedesktop.NetworkManager by reaching out to all devices associated
with the primary connection, and querying their properties, both for
wifi devices and cross-referencing to Ofono for modem devices. This
behavior of not relying on cached values causes excessive traffic on the
bus. The branch attached to this bug mitigates the issue by:

  (1.) Relying on the cached devices for querying device properties. This is sufficient, as the cache is always consistent in this particular scenario.
  (2.) Not explicitly reacting to modem state changes coming in via Ofono but instead only reacting to changes to the PrimaryConnection property of NetworkManager.

** Branch linked: lp:~thomas-voss/location-service/fix-1394204

** Description changed:

  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
+ 
+ TEST CASE: 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.

** Description changed:

  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
  
- TEST CASE: 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  
+ 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.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1394204

Title:
  dbus daemon spinning with NM AP properties change event

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Location Service:
  New
Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu RTM:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394204/+subscriptions