Lennart Poettering

> (I don't see it though ;-) oh, i pushed it onto my copy of the repo by accident. fixed now. sorry for the confusion.

hmm, why did you file this as bug against systemd? This seems to be an Apparmor policy issue? what does thta have to do with us upstream? we do not...

So, there is apparently one process that took the lock on /dev/console and doesn't give it up anymore. Which one is that? "lslocks" should tell you.

Judging by those logs tcsetattr() on your console which points to /dev/ttyS0 freezes. Apparently your /dev/console is simply hosed and that breaks down everything? What's going on there? /dev/console matters,...

> 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 it not...

> > 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...

> > 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? What does `systemctl status serial-getty@ttyS0` say? We need to figure out how that got instantiated. ``` #2 0x00005565f7ba9e64 in...

@eku so, this appears to hang in tcsetattr() for you. I have the strong suspicion that this hang will go away if we switch from TCSADRAIN to TCSANOW as argument...

> Well, since this PR is already merged, I will be waiting for an updated package from Fedora. Note that this might take months, until it reaches Fedora, and while...