On 29 August 2016 at 13:13, Pete Batard <p...@akeo.ie> wrote: > Well, adding 'systemd.log_level=debug' to my kernel options made the system > enter emergency mode... > > And I can't get the very beginning of the log then (even though I also tried > to increase the buffer size by adding 'log_buf_len=19'), so I'm attaching > the best I can provide in terms of verbose log, with the first 4.5 seconds > missing. > > Also attached is the status (from the system running without > 'systemd.log_level=debug', since I don't really want to keep it in emergency > mode).
Thanks. This status file reports that Seccomp: 0. But your kernel doesn't really have seccomp, so that is weird. > But again, as far as I am concerned, one of the changes that intervened > between 231-4 and 231-5 seems to have reverted the SECCOMP issue, so I would > invite you to closely review what was changed between these 2 revisions, as > maybe you'll find a clue there. Well, to work around this problem we (temporarily) disabled all seccomp security filters. With 231-5 we replaced that in favor of runtime detection of seccomp availability. Clearly the runtime detection is insufficient, but we really need to fix the detection: disabling security features is a bug too! I'm trying to install a vm using the debian kernel. This should make it easier to test stuff. -- Saludos, Felipe Sateler
