As I replied to that (did you see it? There may have been some problems with my email about that time), commenting out the “SystemCallFilter” did not make the problem go away on either of the ARM systems.
Another interesting datapoint: I upgraded my PowerMac G4 powerpc machine to latest Sid (including the systemd version in question) and it does *not* have the problem. This is the same result I saw on the amd64 (virtual) machine. So it seems to be arm specific… Any thoughts? On Jul 29, 2016, at 3:02 PM, Michael Biebl <bi...@debian.org> wrote: > Am 29.07.2016 um 23:29 schrieb Rick Thomas: >> Hmmm… Curiouser and curiouser! >> >> I upgraded a VM (amd64) to latest Sid (with systemd version 231-1). The >> problem is *not* present there. >> >> The problem may be specific to arm hardware? I’ll try it on a PowerPC G4 >> (Apple Mac PPC) machine later today. > > I think this might be arch specific, yes. > See my reply earlier: > >> SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount >> @obsolete @raw-io >> >> is causing the problem? If you comment out that line from >> systemd-journald.service, does it start properly? >> >> SystemCallFilter uses libseccomp, maybe libseccomp on armel is not fully >> functional and we need to reassign this. > > > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? >
