[Letux-kernel] Strange things happening with latest kernels

[H. Nikolaus Schaller]

> Am 13.06.2019 um 11:08 schrieb H. Nikolaus Schaller <hns at goldelico.com>:
> 
> Hi Andreas,
> 
>> Am 13.06.2019 um 07:47 schrieb Andreas Kemnade <andreas at kemnade.info>:
>> 
>> Hi Nikolaus,
>> 
>> On Thu, 13 Jun 2019 07:37:46 +0200
>> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
>> 
>>> Hi Andreas,
>>> great analysis!
>>> 
>>> Maybe I was lucky with my GTA04A4 where I tried these days.
>>> 
>>> A theory is that if the opp voltages are not supported, they are not changed and the value initialized
>>> by U-Boot is kept. This will be wrong depending on clock speed.
>>> 
>> Well, the whole frequency-scaling thing seems to be disabled.
>> 5.1 seems still to work. I have reasonable percentages for 300Mhz here.
>> 
>>> I remember there was a discussion these days on linux-omap for the DRA7 about similar regulator issues,
>>> but have forgotten the details.
>>> 
>>> So we should notify Tony about this.
>>> 
>> will probably write an email this evening about that. Unfortunately my autobuild
>> was not active when the things were merged into linus/master. So I have only the
>> interesting logs about linux-next
> 
> I can confirm that the issue is OMAP3 (twl4030) only and not on the Pyra.
> And your patch makes cpufreq-info become available again.
> 
> And I have done some more tests and it looks as if power consumption
> (battery current if not charging) in idle has gone up from letux-4.19(.0)
> to 4.19.44 and again for 4.19.49 by ca. 50mA.
> 
> This happens if X11 is disabled or enabled. With X11 I have ca. 50-60% in
> 800 MHz OPP although the CPU load is below 10%.
> 
> Well, it may also be some repeating background activity which may prevent
> lower clock in my GUI setup (have used QuantumSTEP and not e.g. LXDE
> and have updated some parts in QuantumSTEP recently).
> 
> Something which needs deeper inspection to understand the influencing
> factors.

As soon as I start X11, temperature goes up. Battery temp to 55.1°C and OMAP3
reports 90°C during charging.

Ca. 10% system load:

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND      
 4136 root      20   0   23520  19124   6776 S 10.9  3.8   0:21.16 loginwindow  
 4123 root      19  -1   22520  13676   9640 S  3.6  2.7   0:07.48 Xorg         
 4639 root      20   0    2980   1684   1384 R  0.7  0.3   0:00.09 top          
  506 root     -51   0       0      0      0 S  0.3  0.0   0:05.86 irq/72-4807+ 
 2858 root      20   0       0      0      0 I  0.3  0.0   0:01.16 kworker/0:0+ 
    1 root      20   0    2372   1228   1092 S  0.0  0.2   0:03.39 init         
    2 root      20   0       0      0      0 S  0.0  0.0   0:00.00 kthreadd     
    3 root       0 -20       0      0      0 I  0.0  0.0   0:00.00 rcu_gp       
    4 root       0 -20       0      0      0 I  0.0  0.0   0:00.00 rcu_par_gp   
    8 root       0 -20       0      0      0 I  0.0  0.0   0:00.00 mm_percpu_wq 
    9 root      20   0       0      0      0 S  0.0  0.0   0:01.04 ksoftirqd/0  
   10 root      20   0       0      0      0 I  0.0  0.0   0:02.76 rcu_preempt  
   11 root      20   0       0      0      0 I  0.0  0.0   0:00.00 rcu_sched    
   12 root      20   0       0      0      0 I  0.0  0.0   0:00.00 rcu_bh       
   13 root      rt   0       0      0      0 S  0.0  0.0   0:00.00 migration/0  
   14 root      20   0       0      0      0 S  0.0  0.0   0:00.00 cpuhp/0      
   15 root      20   0       0      0      0 S  0.0  0.0   0:00.01 kdevtmpfs    

root at letux:~# ./temperatures 
:39:27 UTC 2000 90° 55° 4011mV 800MHz
root at letux:~# ./charger 

Battery /sys/class/power_supply/bq27000-battery
==================
type: Battery
present: 1
technology: Li-ion
capacity: 63%
status: Charging
level: Normal
volt: 4004000uV
current: -366282uA
temp: 55.1°C
charge: 564438uAh
full: 891246uAh
design: 1233792uAh
energy: J?
power: W?
cycles: 123
health: Good
discharge: s to empty average
remaining: s to empty
charging: 4740s to full

I have never observed that before. It happens on two different devices. This
was with letux-4.19.49. Next I'll try with letux-4.19.0.

BR,
Nikolaus