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 30 August 2016 at 13:32, Pete Batard wrote:
> 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 af
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
On 30 August 2016 at 13:26, Pete Batard wrote:
> 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 (wh
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
On 29 August 2016 at 13:13, Pete Batard 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
