Ask / Submit
3

[bug] Sony Xperia XA2 kernel thread CPU usage when device locked

asked 2019-02-20 11:20:23 +0200

Georgi Kolev gravatar image

updated 2019-02-20 13:37:35 +0200

HW: Sony Xperia XA2 Single Sim SW: SailfishOS 3.0.1.14

After the device is locked, one of the kernel threds (kworker/u16:0) starts eating CPU and logs start looping on: Reproducible on every device lock

[  +0.000119] Freezing of tasks aborted after 0.010 seconds
[  +0.000316] Restarting tasks ... done.
[  +0.036751] PM: suspend exit 2019-02-20 09:18:08.626027875 UTC
[  +0.052500] ## mmc1: gpio_set failure: ctx=ffffffd1704dd118, uim2_gpio=-22
[  +0.016822] PM: suspend entry 2019-02-20 09:18:08.695346076 UTC
[  +0.000020] PM: Syncing filesystems ... done.
[  +0.049041] Freezing user space processes ... 
[  +0.009811] PM: Wakeup pending, aborting suspend
[  +0.000054] active wakeup source: qcom_rx_wakelock

[  +0.000120] Freezing of tasks aborted after 0.009 seconds
[  +0.000246] Restarting tasks ... done.
[  +0.036089] PM: suspend exit 2019-02-20 09:18:08.790730771 UTC
[  +0.048409] ## mmc1: gpio_set failure: ctx=ffffffd1704dd118, uim2_gpio=-22
[  +0.016298] PM: suspend entry 2019-02-20 09:18:08.855430860 UTC
[  +0.000025] PM: Syncing filesystems ... done.
[  +0.054175] Freezing user space processes ... 
[  +0.009974] PM: Wakeup pending, aborting suspend
[  +0.000053] active wakeup source: qcom_rx_wakelock

[  +0.000120] Freezing of tasks aborted after 0.010 seconds
[  +0.000337] Restarting tasks ... done.
[  +0.036563] PM: suspend exit 2019-02-20 09:18:08.956682987 UTC
[  +0.046623] ## mmc1: gpio_set failure: ctx=ffffffd1704dd118, uim2_gpio=-22
[  +0.069602] PM: suspend entry 2019-02-20 09:18:09.072890960 UTC
[  +0.000026] PM: Syncing filesystems ... done.
[  +0.062453] Freezing user space processes ... 
[  +0.009908] PM: Wakeup pending, aborting suspend
[  +0.000055] active wakeup source: qcom_rx_wakelock

[  +0.000118] Freezing of tasks aborted after 0.010 seconds
[  +0.000245] Restarting tasks ... done.
[  +0.037162] PM: suspend exit 2019-02-20 09:18:09.182877075 UTC
[  +0.045455] ## mmc1: gpio_set failure: ctx=ffffffd1704dd118, uim2_gpio=-22
[  +0.066035] PM: suspend entry 2019-02-20 09:18:09.294357665 UTC
[  +0.000025] PM: Syncing filesystems ... done.
[  +0.057235] Freezing user space processes ... 
[  +0.010140] PM: Wakeup pending, aborting suspend
[  +0.000097] active wakeup source: qcom_rx_wakelock

[  +0.000109] Freezing of tasks aborted after 0.010 seconds
[  +0.000254] Restarting tasks ... done.
[  +0.036612] PM: suspend exit 2019-02-20 09:18:09.398836451 UTC
[  +0.047686] ## mmc1: gpio_set failure: ctx=ffffffd1704dd118, uim2_gpio=-22
[  +0.018750] PM: suspend entry 2019-02-20 09:18:09.465267160 UTC
[  +0.000024] PM: Syncing filesystems ... done.
[  +0.055383] Freezing user space processes ... 
[  +0.010310] PM: Wakeup pending, aborting suspend
[  +0.000111] active wakeup source: qcom_rx_wakelock

[  +0.000109] Freezing of tasks aborted after 0.010 seconds
[  +0.000180] Restarting tasks ... done.
[  +0.036426] PM: suspend exit 2019-02-20 09:18:09.567814909 UTC
[  +0.051878] ## mmc1: gpio_set failure: ctx=ffffffd1704dd118, uim2_gpio=-22
[  +0.013692] PM: suspend entry 2019-02-20 09:18:09.633387860 UTC
[  +0.000013] PM: Syncing filesystems ... done.
[  +0.056009] Freezing user space processes ... 
[  +0.009882] PM: Wakeup pending, aborting suspend
[  +0.000046] active wakeup source: qcom_rx_wakelock

Any suggestions?

Edit:

[  +0.048409] ## mmc1: gpio_set failure: ctx=ffffffd1704dd118, uim2_gpio=-22

Was caused due to no SD card in the slot. After adding a card, that line is not observed anymore.

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted
2

answered 2019-02-20 13:15:11 +0200

spiiroin gravatar image

Assuming that by "device locked" you meant that display is off, and there is nothing to keep the device from suspending: Inspecting live journal over wlan connection is enough to cause this. Some info at https://together.jolla.com/question/141825/high-cpu-activity-with-screen-off/

edit flag offensive delete publish link more

Comments

2

Aha ...got it... seems like screwed up timing on when what should happen.

After putting SD card in the slot the mmc1 error is gone... will dig into a bit more to see what's causing the battery drain while idle without being connected over wifi

Georgi Kolev ( 2019-02-20 13:36:14 +0200 )edit
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2019-02-20 11:20:23 +0200

Seen: 202 times

Last updated: Feb 20