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. 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 > <[email protected]> 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 : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
