Arch Linux

mohan

Member

Registered: 2019-03-03

Posts: 3

Errors after suspending to ram with systemctl

Hey, newbie here!

I was getting some error on some applications(android-studio, adb, geckodriver) after suspending session to ram with systemctl comand :

# systemctl suspend 

, everything works fine if i echo mem in /sys/power/state

#echo mem > /sys/power/state

or

# /usr/lib/systemd/systemd-sleep suspend

.

Error in adb.

# adb start-server                                                      
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /tmp/adb.1000.log
Server had pid: 2254
--- adb starting (pid 2254) ---
adb I 11-05 16:29:52  2254  2254 main.cpp:60] Android Debug Bridge version 1.0.41
adb I 11-05 16:29:52  2254  2254 main.cpp:60] Version 29.0.4-5871666
adb I 11-05 16:29:52  2254  2254 main.cpp:60] Installed as /opt/android-sdk/platform-tools/adb
adb I 11-05 16:29:52  2254  2254 main.cpp:60] 
adb F 11-05 16:29:52  2254  2254 main.cpp:144] could not install *smartsocket* listener: Cannot assign requested address

* failed to start daemon
error: cannot connect to daemon

error in android studio

$ android-studio                                                       
Failed to find the loopback interface

Cannot Lock System Folders: Internal error. Please report to https://code.google.com/p/android/issues

java.net.BindException: Cannot assign requested address
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:130)
	at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:562)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1358)
	at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:501)
	at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:486)
	at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:1019)
	at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:258)
	at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:366)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:474)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:909)
	at java.lang.Thread.run(Thread.java:748)

and last error in geckodriver

$ geckodriver
1572951805280	geckodriver	ERROR	Cannot assign requested address (os error 99)

My system info

kernel parameters :

resume=/dev/sda3 acpi_backlight=vendor aspi_osi=Linux ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 iommu=pt

mkinitcpio hooks :

HOOKS=(base udev autodetect modconf block filesystems resume keyboard fsck)

linux kernel version :

5.1.8-arch1-1-ARCH

please reply if you want some more information

Last edited by mohan (2019-11-05 13:42:32)

teckk

Member

Registered: 2013-02-21

Posts: 519

Re: Errors after suspending to ram with systemctl

5.1.8-arch1-1-ARCH

adb I 11-05 16:29:52  2254  2254 main.cpp:60] Version 29.0.4-5871666

I'm a couple weeks out of date and I have
pacman -Si android-tools

Repository      : community
Name            : android-tools
Version         : 29.0.4-2
...

Are you partially updated? Or just holding the kernel back? Which is in itself a partial update. What do you have going on?

mohan

Member

Registered: 2019-03-03

Posts: 3

Re: Errors after suspending to ram with systemctl

5.1.8-arch1-1-ARCH

adb I 11-05 16:29:52  2254  2254 main.cpp:60] Version 29.0.4-5871666

I'm a couple weeks out of date and I have
pacman -Si android-tools

Repository      : community
Name            : android-tools
Version         : 29.0.4-2
...

Are you partially updated? Or just holding the kernel back? Which is in itself a partial update. What do you have going on?

Yes, my android-tools package is updated and 5.1.8 + Linux kernels work like shit in my laptop thats why I haven't updated it.

mohan

Member

Registered: 2019-03-03

Posts: 3

Re: Errors after suspending to ram with systemctl

Fixed : This was an kde's problem not kernel or anything after uninstalling kde everything worked fine with latest kernel 5.3.10-arch1-1

seth

Member

Registered: 2012-09-03

Posts: 51,056

Re: Errors after suspending to ram with systemctl

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc