ubuntu-phone team mailing list archive

[Matthias Apitz <guru@xxxxxxxxxxx>]

El día Saturday, April 23, 2016 a las 06:18:57PM -0400, Skyflyer escribió:

> I used "echo l > /proc/sysrq-trigger" to run a backtrace of all cpus. 
> Output will be logged in dmesg.  Watching syslog or dmesg with "Adjust
> brightness automatically" on and off will show a big difference in the
> log files, specifically this line:
> 
> (0)[1576:kworker/0:2][ALS/PS] als_get_data 1962 : als_get_data *value =
> 140, *status =2
> 
> I get a million of these in syslog with auto brightness turned on.

Me too. I saw these lines as well in /var/log/syslog:

Apr 17 06:17:01 ubuntu-phablet kernel: [23390.162827] (0)[17343:kworker/0:0][ALS/PS] als_get_data 1962 : als_get_data *value = 10, *status =2
Apr 17 06:17:01 ubuntu-phablet kernel: [23390.172843] (0)[17343:kworker/0:0][ALS/PS] als_get_data 1962 : als_get_data *value = 10, *status =2
Apr 17 06:17:01 ubuntu-phablet kernel: [23390.182819] (0)[17343:kworker/0:0][ALS/PS] als_get_data 1962 : als_get_data *value = 10, *status =2
Apr 17 06:17:01 ubuntu-phablet kernel: [23390.192814] (0)[17343:kworker/0:0][ALS/PS] als_get_data 1962 : als_get_data *value = 10, *status =2
Apr 17 06:17:01 ubuntu-phablet kernel: [23390.203703] (0)[17343:kworker/0:0][ALS/PS] als_get_data 1962 : als_get_data *value = 10, *status =2
Apr 17 06:17:01 ubuntu-phablet kernel: [23390.212825] (0)[17343:kworker/0:0][ALS/PS] als_get_data 1962 : als_get_data *value = 10, *status =2
Apr 17 06:17:01 ubuntu-phablet kernel: [23390.222821] (0)[17343:kworker/0:0][ALS/PS] als_get_data 1962 : als_get_data *value = 10, *status =2

I only did not understand where they come from. I should have googled
around?

One of the biggest problem for me at the moment is the battery drain.
Even over night, when my M10 is unused, there is always a drain of some
5% per hour. There must be something which does not let the M10 go to
deep suspend...

We should file a bug issue in LP, I think.

	matthias

PS: I have changed the Subject:

-- 
Matthias Apitz, ✉ guru@xxxxxxxxxxx, ⌂ http://www.unixarea.de/  ☎ +49-176-38902045
¡Dios querido denos otra vez los problemas de ayer, los que tuvimos en la RDA!
My Lord, give us back the problems of yesterday, those we have had in the GDR.
> 
> Are you seeing the same thing?
> 
> 
> On 04/23/2016 02:37 AM, Matthias Apitz wrote:
> > El sábado, 23 de abril de 2016 7:18:17 (CEST), Will Atwood
> > <skyflyer@xxxxxxxxxxxx> escribió:
> >> I'm also a new FHD M10 owner and am really excited to have one.. I'm
> >> using it now to type this up...on screen keyboard is working well..
> >> My biggest issue so far was high CPU load with kworker...around 26%
> >> or so.. Syslog was getting flooded with errors so I ran a CPU
> >> backtrack and pinpointed the camera sensor.. Thought that was strange
> >> until I realized it is being used to adjust screen brightness!. If
> >> your seeing unusually high CPU load at idle...try disabling “adjust
> >> brightness automatically”.  That made a big difference for me.
> >>
> >> The next syslog issue I'm seeing is CPU freq scalling....anyone have
> >> any ideas?
> >>
> >>
> >
> > Hi Will,
> >
> > Awesom! I'm facing this CPU kworker problem too for some time already and
> > could not get to the point. Could you please share how you nailed this
> > down, just
> > for the next problem like this.
> >
> > Thanks
> >
> >     matthias
> >
> >
> >
> 
> 
> -- 
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp

-- 
Matthias Apitz, ✉ guru@xxxxxxxxxxx, ⌂ http://www.unixarea.de/  ☎ +49-176-38902045
¡Dios querido denos otra vez los problemas de ayer, los que tuvimos en la RDA!
My Lord, give us back the problems of yesterday, those we have had in the GDR.