Help: Pinebook Pro will not enter sleep [Manjaro 20.04]
#1
Question 
Hello, I just received my Pinebook Pro yesterday which is the latest Manjaro branded version using the most current Manjaro ARM KDE 20.04 release. I finally finished installing & configuring all of my software/settings and thought I would test the machine - everything seems to work fine except SLEEP! (I also have a thread open about this issue on Manjaro forums since I'm not sure which would be the better place)

I have researched online and see a few others have encountered similar issues, but I wasn't able to find a fix that worked for me. Also, I haven't made any configuration changes or messed with suspend modes - I am fine with using s2idle, just want the screen to shut off and sleep when I close the laptop lid!

The crux of the issue is that the laptop starts to go to sleep, then it wakes immediately after - whether closing the lid, pressing the power button and choosing "sleep", or typing into terminal: "systemctl suspend". Long story short, it appears that either the dwmmc_rockchip [fe310000.mmc: pre_suspend failed for non-removable host: -38], or Device ff9a0000.gpu [failed to suspend: error -16] are causing the machine to abort going to sleep. Attached are the full logs:

Code:
May 28 12:15:59 feather polkitd[1013]: Registered Authentication Agent for unix-process:4179:71609 (system bus name :1.193 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale eaHello, I just received my Pinebook Pro yesterday which is the latest Manjaro branded version using the latest Manjaro ARM KDE 20.04 release. n_US.UTF-8)
May 28 12:15:59 feather ksmserver[1216]: lock called
May 28 12:15:59 feather kded5[1188]: bluedevil: About to suspend
May 28 12:15:59 feather NetworkManager[881]: <info>  [1590693359.2819] manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 28 12:15:59 feather NetworkManager[881]: <info>  [1590693359.2822] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 28 12:15:59 feather NetworkManager[881]: <info>  [1590693359.2842] manager: NetworkManager state is now ASLEEP
May 28 12:15:59 feather ksmserver[1216]: Lock window Id:  20971562
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 20971562
May 28 12:15:59 feather polkitd[1013]: Unregistered Authentication Agent for unix-process:4179:71609 (system bus name :1.193, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 28 12:15:59 feather org_kde_powerdevil[1269]: powerdevil: Pausing all media players before sleep
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525956
May 28 12:15:59 feather kscreenlocker_greet[4185]: Qt: Session management error: networkIdsList argument is NULL
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525960
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525972
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525981
May 28 12:16:00 feather kscreenlocker_greet[4185]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Breath2/contents/images/"
May 28 12:16:00 feather kscreenlocker_greet[4185]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Breath2/contents/images/"
May 28 12:16:00 feather kscreenlocker_greet[4185]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Breath2/contents/images/"
May 28 12:16:00 feather kscreenlocker_greet[4185]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
May 28 12:16:00 feather kscreenlocker_greet[4185]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54525983
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54525985
May 28 12:16:00 feather ksmserver[1216]: MapNotify: 54525983
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 41947667
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54525987
May 28 12:16:00 feather ksmserver[1216]: MapNotify: 20971562
May 28 12:16:00 feather systemd[1]: Reached target Sleep.
May 28 12:16:00 feather systemd[1]: Starting Suspend...
May 28 12:16:00 feather kscreenlocker_greet[4185]: UdevQt: unable to create udev monitor connection
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54526000
May 28 12:16:00 feather kscreenlocker_greet[4185]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
May 28 12:16:01 feather kscreenlocker_greet[4185]: file:///usr/share/plasma/look-and-feel/org.kde.breath2.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
May 28 12:16:01 feather ksmserver[1216]: CreateNotify: 54526011
May 28 12:16:01 feather systemd-sleep[4193]: Suspending system...
May 28 12:16:01 feather kernel: PM: suspend entry (s2idle)
May 28 12:16:02 feather kernel: Filesystems sync: 0.060 seconds
May 28 12:16:02 feather kernel: dwmmc_rockchip fe310000.mmc: pre_suspend failed for non-removable host: -38
May 28 12:16:02 feather kernel: Freezing user space processes ... (elapsed 0.004 seconds) done.
May 28 12:16:02 feather kernel: OOM killer disabled.
May 28 12:16:02 feather kernel: Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
May 28 12:16:02 feather kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 28 12:16:02 feather kernel: PM: dpm_run_callback(): pm_runtime_force_suspend+0x0/0xd8 returns -16
May 28 12:16:02 feather kernel: PM: Device ff9a0000.gpu failed to suspend: error -16
May 28 12:16:02 feather kernel: PM: Some devices failed to suspend, or early wake event detected
May 28 12:16:02 feather kernel: OOM killer enabled.
May 28 12:16:02 feather kernel: Restarting tasks ... done.
May 28 12:16:02 feather kernel: PM: suspend exit
May 28 12:16:02 feather wpa_supplicant[923]: wlan0: CTRL-EVENT-DISCONNECTED bssid=38:94:ed:c5:0b:17 reason=3 locally_generated=1
May 28 12:16:02 feather systemd-networkd[518]: wlan0: Lost carrier
May 28 12:16:02 feather wpa_supplicant[923]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 28 12:16:02 feather systemd-sleep[4193]: Failed to suspend system. System resumed again: Device or resource busy
May 28 12:16:03 feather systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
May 28 12:16:03 feather systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
May 28 12:16:03 feather systemd[1]: Failed to start Suspend.
May 28 12:16:03 feather systemd[1]: Dependency failed for Suspend.
May 28 12:16:03 feather systemd-logind[886]: Operation 'sleep' finished.

This suspend issue is happening on my eMMC main installation, but also happens on a fresh SD card install of Manjaro ARM KDE 20.04 as well with the same error messages as above. Also, interesting to note that this Pinebook Pro also has actually successfully entered sleep state before - it will randomly work maybe 5% of the time, which hopefully is a good sign this is a software issue that can be fixed.

Loving this little machine other than this issue - Any help is greatly appreciated, thank you!
  Reply
#2
Facing the same thing here with the default Manjaro installation and all the updates installed.

It's mostly annoying as I can't trust closing the lid will enter sleep. So I've now resorted to first put the machine to sleep a few times until it actually sleeps, and then close the lid. Which is less than ideal.

If a solution is found, I'd be keen to try it Smile
  Reply
#3
I don't know if it helps but I noticed that if after using the laptop for a while I kill pulseaudio, I've been able to sleep on first try every time.

What I'm doing is: pulseaudio -k

It should be safe as pulseaudio should auto-restart.

I've started doing this as on occasion my audio stack completely dies and I get no audio from videos, etc. But killing pulseaudio solves that issue, and seems to have been solving the sleep issue for me too.
  Reply
#4
Nevermind my post above... It happened again right after I had done a pulseaudio -k ... so definitely unrelated.
  Reply
#5
Ah... this explains why my PBP has a depleted battery in the morning when I wake up... :p
  Reply
#6
Yep, just got my PBP Saturday, and noticed today that the device won't go to sleep, whether on or off AC. I don't really know if an update caused the issue or not, as I downloaded updates within the first 15 minutes of starting the machine up (after I figured out that wifi was disabled on the hardware).
  Reply
#7
AFAIK, it's one of the last real 'known issue' bugs waiting to be put to rest. Usually sleep works only once for me... the first time I use it. After waking up the PBP, it won't go to sleep, usually with the `ff9a0000.gpu` device waking it up again/preventing it from sleeping. I haven't seen the `fe310000.mmc` one before, which IIRC is the WiFi card. I haven't tried repeatedly putting it to sleep, so I don't what if there are other tricks like killing pulseaudio, etc. that will make it more likely to behave. So rest assured, it's not just you, and it's not a new behaviour! I think the Manjaro guys were a bit naughty, it was a known issue in 19.12 (Suspend does not work on the Pinebook Pro), and fell off the list in the 20.02/20.04 release notes, even though it still isn't stable/reliable.
  Reply
#8
On the default Manjaro + KDE; when I tried to suspend. The GPU woke up and prevented the suspend.
I tried Kali and exactly the same issue.

I tried Manjaro + XFCE and it suspends no problem. The issue is that it's Suspend to Idle. It's practically worthless as a suspend because it's still burning 4%/battery/hour.

When I configure for Deep suspend to ram (which is the ideal option) it does seem to go into deep suspend; but then I cannot unsuspend and similarly need to hold power button to shutdown.
  Reply
#9
(06-04-2020, 09:51 AM)sleepingsysadmin Wrote: When I configure for Deep suspend to ram (which is the ideal option) it does seem to go into deep suspend; but then I cannot unsuspend and similarly need to hold power button to shutdown.

To get s3 to work correctly, replace the mainline u-boot on your install with the BSP u-boot from mrfixit's v2 branch. There's a link in the wiki to the files.
  Reply
#10
I noticed this too - closing the lid usually doesn't suspend. Manually selecting the "suspend to RAM" action from the KDE menu sometimes works.

Is there anywhere else where I can follow progress and potentially help testing fixes/workarounds? Maybe with the Manjaro or KDE Plasma folks?
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  which distro + DE are you using these days on the Pinebook Pro? halogen 16 686 Yesterday, 12:23 AM
Last Post: calinb
  Sound stuttering on Manjaro gnome after latest kernel upgrade? pjsf 0 109 07-13-2021, 10:37 PM
Last Post: pjsf
  Kernel crash on Manjaro ARM mfashby 0 119 07-06-2021, 03:17 PM
Last Post: mfashby
  postmarketOS/Alpine edge image for the Pinebook Pro MartijnBraam 71 49,088 07-03-2021, 02:40 PM
Last Post: user526
Bug 4K@30 video output does not work properly on Pinebook Pro jkm 0 166 06-29-2021, 08:43 AM
Last Post: jkm
  Manjaro wont recognize eMMC after booting with it disabled peasant 1 223 06-27-2021, 02:39 AM
Last Post: Arwen
  A true mainline Linux Kernel for the Pinebook Pro tsys 154 98,761 06-20-2021, 09:26 AM
Last Post: linuxad
  Pinebook pro nearly unusable after using manjaro-arm-installer TheCounselor 0 262 06-18-2021, 03:34 PM
Last Post: TheCounselor
  Pinebook Pro Manjaro Power Savinng Tips HelpMyBatteryIsDraining 1 363 06-15-2021, 08:42 AM
Last Post: moonwalkers
  [LibreOffice & Gimp] ARM support: no hardware acceleration on [Manjaro] Pinebook Pro regivanx 0 242 06-15-2021, 04:04 AM
Last Post: regivanx

Forum Jump:


Users browsing this thread: 1 Guest(s)