Yes! At long last 231-6 seems to have cleared the systemd issue I was
observing on Raspberry Pi:
--
root@pi ~ # systemctl status
● pi
State: running
Jobs: 0 queued
Failed: 0 units
Okay.
I have logged issue #651
(https://github.com/raspberrypi/firmware/issues/651) with the rpi team
so that they try to sort their SECCOMP configuration in future kernels.
Regards,
/Pete
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maint
On 2016.08.30 17:30, Felipe Sateler wrote:
I managed to get the config from a jessie rpi by loading the 'configs'
module (sudo modprobe configs). After that the config is found on
/proc/config.gz
Yeah, I just discovered the same after I replied.
This is also documented on the official rpi githu
Thanks Felipe.
I guess with the new detection process, the resurgence of the issue is
starting to make sense now.
For the record, I am using one of the latest official Raspberry Pi
kernels from https://github.com/raspberrypi/firmware (which I get
indirectly through the https://github.com/Hex
Please find my boot log. Note that I've tried commenting out
'MemoryDenyWriteExecute=yes' in the various .service config files, but
it didn't help.
If you need anything else, please let me know.
Regards,
/Pete
[0.00] Booting Linux on physical CPU 0xf00
[0.00] Initializing cgro
On 2016.08.28 15:37, Felipe Sateler wrote:
Could you try 231-5 from unstable?
Oops, I mean 231-5 broke it. I'm seeing the issue back in 231-5 and not
231-4 as I mentioned earlier.
231-4 seemed to be okay, and it's only when I upgraded to 231-5 that the
problem reappeared.
Regards,
/Pete
...and 231-4 broke the whole thing down again. :(
Same error:
root@pi ~ # systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service;
s
Didn't fix it for me... :(
I went to an 'apt-get --reinstall install' of every single package that
is listed under 'Description' above (expect -udeb and -dev), and got the
231-2 version alright, but the issue remains exactly the same, even
after a full reboot.
I should point out that I did g
