Rootston freezes on ssh log out
After a couple of minutes of no activity, the lock screen will freeze, and its contents will not get updated no matter what.
The situation can be fixed by issuing systemctl restart phosh
.
last lines of dmesg dmesg:
[ 4807.890960] etnaviv-gpu 130000.gpu: genpd_runtime_suspend()
[ 4828.364971] etnaviv-gpu 130000.gpu: genpd_runtime_resume()
[ 4828.900932] etnaviv-gpu 130000.gpu: genpd_runtime_suspend()
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Owner
I can't reproduce this. I've been running previous versions of wlroots/phosh for several days on the nitrogen6 and I've been using the current version for several hours. Can you debug further?
I have seen issues where wlroots would freeze when closing out of the ssh session that started it. Could that be your issue (I've not debugged this further yet since it's started during boot).
- Owner
$ uptime 14:07:12 up 1 day, 23:13, 2 users, load average: 0.25, 0.10, 0.03
Lockscreen still responsive.
- Owner
Steps to reproduce:
$ ssh nitrogenboard $ systemctl restart phosh $ exit
Relevant log entries:
Jul 20 14:51:58 pureos systemd-logind[362]: Removed session 26. Jul 20 14:51:59 pureos rootston[1284]: 2018-07-20 14:51:59 - [backend/drm/backend.c:95] DRM fd paused Jul 20 14:51:59 pureos rootston[1284]: 2018-07-20 14:51:59 - [backend/session/logind.c:226] SessionRemoved signal received
with that wlroots suspends input and output devices.
Edited by Guido Gunther - Guido Gunther changed title from Lock screen freezes on imx6 to Rootston freezes on ssh log out
changed title from Lock screen freezes on imx6 to Rootston freezes on ssh log out
- Guido Gunther mentioned in merge request !12 (closed)
mentioned in merge request !12 (closed)
- Owner
I've changed the bug title so we only track one issue. If there are other freeze causes let's open separate bugs. !12 (closed) shows that the device pause is indeed the cause of the problem.
- Guido Gunther changed the description
changed the description
- Guido Gunther mentioned in issue virtboard#15
mentioned in issue virtboard#15
- Dorota Czaplejewicz mentioned in merge request !35 (closed)
mentioned in merge request !35 (closed)
- Owner
We should check what happens when we use
pam_systemd.so
in the pam stack. - Guido Gunther mentioned in issue #18 (closed)
mentioned in issue #18 (closed)
- Owner
I've not seen this since ages so it seems to be fixed with newer systemd, o.k. to close?
- Author Maintainer
I haven't seen it either, so I'll close. We can reopen when we notice it again.
- Dorota Czaplejewicz closed
closed
- Guido Gunther mentioned in merge request linux-emcraft!22
mentioned in merge request linux-emcraft!22
- Guido Gunther reopened
reopened
- Guido Gunther mentioned in issue phosh#70 (closed)
mentioned in issue phosh#70 (closed)
- Guido Gunther mentioned in issue #24 (moved)
mentioned in issue #24 (moved)
- Maintainer
Just confirming that it occurs following an
scp
into the device over Ethernet (see phosh#70 (closed)):May 10 13:27:08 pureos phosh[2208]: 2019-05-10 13:27:08 - [backend/drm/backend.c:100] DRM fd paused May 10 13:27:08 pureos phosh[2208]: 2019-05-10 13:27:08 - [backend/session/logind.c:227] SessionRemoved signal received
uname -a
givesLinux pureos 4.18.11-gd910c0d1 #1 SMP PREEMPT Wed May 8 10:32:57 PDT 2019 aarch64 GNU/Linux
systemd is version 241-3.
Edited by Heather Ellsworth