Erik Kunze
Erik Kunze
``` # lslocks --notruncate |grep console (agetty) 6317 FLOCK WRITE* 0 0 0 /dev/console (agetty) 586374 FLOCK WRITE* 0 0 0 /dev/console (agetty) 2662 FLOCK WRITE* 0 0 0 /dev/console...
> Judging by those logs tcsetattr() on your console which points to /dev/ttyS0 freezes. So you mean that it accesses /dev/ttyS0. Kernel command line does not configure ttyS0 as console....
> The relevant logic was added by [3390be3](https://github.com/systemd/systemd/commit/3390be38d19c9d339bbc0e003743ce4278aa58b6) and [3f2e8e9](https://github.com/systemd/systemd/commit/3f2e8e951ace01b2f7da6ac45bd24e4c7a73eb91) and both are in v257. Thanks for pointing this out. That explains why the update from 256 to 257 locks...
> > systemd-getty-creator created a unit definition for ttyS0. This one ist inside the chipset and not connected to the outside. > > How could this happen? And, why did...
> So, how come you have a a service connected to /dev/ttyS0? Something created a link from `/etc/systemd/system/getty.target.wants/[email protected]` to `/usr/lib/systemd/system/[email protected]`. I'm pretty sure that it was not created manually. I...
> Is `[email protected]` recreated after `systemctl daemon-reload` or `systemctl daemon-reexec`? Nope.
> Any chance you can apply that to your tree, and check if this fixes the issue for you, even if you have the faulty [[email protected]](mailto:[email protected]) enabled on your system?...
> Did you find the actual reason? According to the MQTT there are two reasons logged: 1 - Vbat power on reset -> I turn it off every night 3...
> It seems for some reason that your system has changed the key provided from the Android KeyStore or the pref value kept behind it. Why should it have changed...