High CPU activity with screen off?

Question

2

High CPU activity with screen off?

Tracked by Jolla (Rejected)

asked 2016-08-16 07:30:45 +0300

tortoisedoc

11414 ●172 ●269 ●287

http://kastlunger.blogspo...

updated 2016-08-16 11:44:23 +0300

vattuvarg

13872 ●197 ●289 ●323

https://wordsmith.social/...

Hey; I happened to be debugging other apps, and had journalctl open, whilst the screen was switched off. It appears there is quite alot going on:

Aug 16 07:27:51 Sailfish kernel: CPU3 is up

Aug 16 07:27:51 Sailfish kernel: PM: noirq resume of devices complete after 1.130 msecs

Aug 16 07:27:51 Sailfish kernel: PM: early resume of devices complete after 1.789 msecs

Aug 16 07:27:51 Sailfish kernel: PM: resume of devices complete after 86.470 msecs

Aug 16 07:27:51 Sailfish kernel: Restarting tasks ... done

Aug 16 07:27:51 Sailfish kernel: PM: suspend exit 2016-08-16 04:27:51.704353752 UTC

Aug 16 07:27:52 Sailfish kernel: PM: suspend entry 2016-08-16 04:27:52.199023804 UTC

Aug 16 07:27:52 Sailfish kernel: PM: Syncing filesystems ... done.

Aug 16 07:27:52 Sailfish kernel: Freezing user space processes ... (elapsed 0.005 seconds) done.

Aug 16 07:27:52 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.

Aug 16 07:27:52 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)

Aug 16 07:27:52 Sailfish kernel: PM: suspend of devices complete after 44.658 msecs

Aug 16 07:27:52 Sailfish kernel: PM: late suspend of devices complete after 2.966 msecs

Aug 16 07:27:52 Sailfish kernel: PM: noirq suspend of devices complete after 3.321 msecs

Aug 16 07:27:52 Sailfish kernel: Disabling non-boot CPUs ...

Aug 16 07:27:52 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend

Aug 16 07:27:52 Sailfish kernel: Enabling non-boot CPUs ...

Aug 16 07:27:52 Sailfish kernel: CPU1 is up

Aug 16 07:27:52 Sailfish kernel: CPU2 is up

Aug 16 07:27:52 Sailfish kernel: CPU3 is up

Aug 16 07:27:52 Sailfish kernel: PM: noirq resume of devices complete after 1.624 msecs

Aug 16 07:27:52 Sailfish kernel: PM: early resume of devices complete after 2.024 msecs

Aug 16 07:27:52 Sailfish systemd[1]: Time has been changed

Aug 16 07:27:52 Sailfish kernel: PM: resume of devices complete after 84.051 msecs

Aug 16 07:27:52 Sailfish kernel: Restarting tasks ... done.

Aug 16 07:27:52 Sailfish kernel: PM: suspend exit 2016-08-16 04:27:52.527181511 UTC

Aug 16 07:27:52 Sailfish systemd[695]: Time has been changed

Can someone help tell what these are?

edit retag flag offensive close delete

Comments

1

Trimmed the headline (and compensated that somewhat by adding a tag). Hopefully that's OK.

vattuvarg ( 2016-08-16 11:43:56 +0300 )edit

Trimmed the headline (and compensated that somewhat by adding a tag). Hopefully that's OK.
vattuvarg ( 2016-08-16 11:43:56 +0300 )edit

Accepted Answer

6

answered 2016-08-16 08:07:50 +0300

spiiroin
13237 ●151 ●224 ●199

moderator

@tortoisedoc: You're connected over wlan, right?

Having kernel log suspend activity + following the logging over wlan connection + wlan that can wake up / keep the device from suspending -> causes recurring suspend attempts.

If you specifically need to debug suspend behavior, redirecting output to a file and inspecting it afterwards / with slight delay should work a bit better. Something like:

journalctl -f > foo &
tail -n+0 -s2 -f foo

Or if you just need to debug display off behavior in general, connecting via usb network / disabling late suspend should do the trick.

mcetool --set-suspend-policy=early

Back to defaults via:

mcetool --set-suspend-policy=enabled

edit flag offensive delete publish link

Comments

I have this problem too, but a tracker-control -rs solves it every time. Some how it gets stuck very frequent on Jolla C dunno why.

Sailor ( 2016-08-17 10:44:35 +0300 )edit

High CPU activity with screen off?

Comments

1 Answer

Comments

Question tools

Stats

Related questions

High CPU activity with screen off?

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions