touch-packages team mailing list archive

[Sebastien Bacher <seb128@xxxxxxxxxx>]

I'm seeing that on killin with the rtm 23 images, gps was turned off and
I switched it on from settings to try if that was working with the here
application

logcat reports that

"--------- beginning of /dev/alog/system
W/SchedPolicy(  907): add_tid_to_cgroup failed to write '34' (Invalid argument); policy=1
W/SchedPolicy(  907): add_tid_to_cgroup failed to write '46' (Invalid argument); policy=1
W/SchedPolicy(  907): add_tid_to_cgroup failed to write '46' (Invalid argument); policy=1
W/SchedPolicy(  907): add_tid_to_cgroup failed to write '46' (Invalid argument); policy=1
E/POAD    (  943): boot_mode = 0
E/POAD    (  943): update boot reason = 0
I/thermal_repeater(  938): START+++++++++ 47
I/thermal_repeater(  938): Success to write 47 to /proc/wmt_tm/tm_pid
I/thermal_repeater(  938): Enter infinite loop
I/sn      (  939): Retry 0
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 1
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 2
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 3
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 4
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 5
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 6
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 7
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 8
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
I/sn      (  939): Retry 9
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Fail to access err=No such file or directory
I/sn      (  939): Check all possible paths
--------- beginning of /dev/alog/main
D/SensorService(  949): dropping 1 events 
..."

the bottom line keeps being repeted

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1358918

Title:
  ubuntu-location-serviced cpu usage spikes to 100% occasionally

Status in “location-service” package in Ubuntu:
  Confirmed

Bug description:
  Occasionally, users report the location service daemon CPU usage to
  spike and occupy an entire core of the system. Up until now, we have
  no way of reliably reproducing the issue. If you encounter it, please
  do the following:

    * Report the output of /system/bin/logcat on this bug
    * If possible, attach to the location service daemon process with:
           * sudo gdb -p ${PID_OF_LOCATION_SERVICE_DAEMON}
           * Call generate-core-file inside gdb
           * Attach the resuling core.${PID_OF_LOCATION_SERVICE_DAEMON} to this bug report

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1358918/+subscriptions