[Jolla Tablet] High standby CPU when not charging, becomes unresponsive

asked 2016-04-11 20:44:57 +0300

Andy Branson gravatar image

updated 2016-05-16 19:04:31 +0300

Edit: I've noticed that my tablet hasn't locked up for several weeks. I'd been keeping it plugged in, but have recently started leaving it unplugged and it seems fine. The cpu usage is still reported as high by top, system monitor and lighthouse, but that may be a problem with reporting the CPU suspend time as usage.


Often after using my tablet I noticed that it would be unresponsive after sitting on standby for a while. I assumed the battery had drained, but after plugging it into a suitable charger and managing to get it to turn on again, the battery would be at 70% or so. After running the System Monitor app for a while, I noticed that these episodes came after a long period of high CPU usage (about 65-80%), which started when the tablet was in standby. It doesn't happen every time, and never when the tablet is charging afaik. System Monitor only told me that these were system processes, not user.

Today I looked a bit further into it, and tried to get something out of top. I can't be sure it's correct, because being connected over ssh stops the tablet suspending properly. I saw a succession of kworker processes take heavy CPU, then get replaced by another. I took some dumps with /proc/sysrq-trigger, but that didn't really give me anything consistent, so I managed to install perf (and less, which for some reason I needed to get from mer-tools). The report gave me the following as the top consumer, and I assume [bcm4330] is driver related. I don't have any debug symbols though, so it's all just numbers.

# Overhead          Command                     Shared Object
# ........  ...............  ................................  ...........................................
#
    86.33%          swapper  [bcm4330]                         [k] 0xffffffff820163a6
                    |
                    |--72.96%-- 0xffffffff8265cd72
                    |          0xffffffff8265cec9
                    |          0xffffffff8265d01e
                    |          0xffffffff8200b11e
                    |          0xffffffff820e2bee
                    |          0xffffffff828d7c5f
                    |          0xffffffff83220e8d
                    |          0xffffffff832205e5
                    |          0xffffffff832206ae
                    |
                    |--20.66%-- 0xffffffff8265cd79
                    |          0xffffffff8265cec9
                    |          0xffffffff8265d01e
                    |          0xffffffff8200b11e
                    |          0xffffffff820e2bee
                    |          0xffffffff828d7c5f
                    |          0xffffffff83220e8d
                    |          0xffffffff832205e5
                    |          0xffffffff832206ae
                    |
                    |--1.86%-- 0xffffffff8265cd70
                    |          0xffffffff8265cec9
                    |          0xffffffff8265d01e
                    |          0xffffffff8200b11e
                    |          0xffffffff820e2bee
                    |          0xffffffff828d7c5f
                    |          0xffffffff83220e8d
                    |          0xffffffff832205e5
                    |          0xffffffff832206ae
                    |
                    |--1.85%-- 0xffffffff8265cd7c
                    |          0xffffffff8265cec9
                    |          0xffffffff8265d01e
                    |          0xffffffff8200b11e
                    |          0xffffffff820e2bee
                    |          0xffffffff828d7c5f
                    |          0xffffffff83220e8d
                    |          0xffffffff832205e5
                    |          0xffffffff832206ae
                     --2.67%-- [...]
edit retag flag offensive close delete

Comments

2

bcm4330
is the driver for the wireless. This is an interesting observation as I had some wifi issues and also suspect the driver: https://together.jolla.com/question/132531/bugtablet-unusable-wifi-connection-drops-dead/

leszek ( 2016-04-11 22:35:47 +0300 )edit

In the comments of this: https://together.jolla.com/question/130228/questions-for-jolla-tablet-owners-about-battery-and-cpu-usage/ someone thought the high idle CPU usage might be due to CPU scaling. While idle the device drops the clocks to save energy except when it is plugged to charger when it runs with full speed all the time.

avhakola ( 2016-04-11 23:38:28 +0300 )edit
2

Lots of useful info on there, I've asked for more perf reports so we can see if everyone has the same issue. If only that had come up when I tried searching before I created this question. They never do though, do they? :)

Andy Branson ( 2016-04-12 01:14:49 +0300 )edit
2

I can confirm this behavior on my brand new tablet, Sailfish up to date. When not charging, the tablet will not wake up with either double tap or power button. When charging the tablet goes to sleep and wakes up just fine. Holding the power button for ten seconds seems to shut if off and a three second press boots it up again. Not so fun.

mingalsuo ( 2016-04-14 22:25:59 +0300 )edit
2

Last night I tried disabling the bcm4330 module to see if it fixed it. The tablet didn't hang, but SysMon still showed the high CPU usage. Couldn't run perf though as no ssh possible without wifi. I could try a cron, or even see if I can connect ethernet to USB-OTG...

Andy Branson ( 2016-04-15 15:30:39 +0300 )edit