Bug#892360: systemd: Breaks also all my tested amd64 machines

* Elimar Riesebieter [2018-03-08 19:13 +0100]: [...] > ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's > wait and see "CONFIG_CGROUP_CPUACCT is not set" gives the same error as shown in the picture of my initial bug report. The problem must be triggerd

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:26 PM, Eric Valette wrote: On 3/8/18 7:13 PM, Elimar Riesebieter wrote: I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd runs fine... Ok. So still in line with hypothesis... ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's wait and see

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:13 PM, Elimar Riesebieter wrote: I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd runs fine... Ok. So still in line with hypothesis... ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's wait and see And I'm rebuilding my failing kernel

Bug#892360: systemd: Breaks also all my tested amd64 machines

* Eric Valette [2018-03-08 19:08 +0100]: > On 3/8/18 7:03 PM, Elimar Riesebieter wrote: > > * Michael Biebl [2018-03-08 18:54 +0100]: > > > > [...] > > > Can you check your custom kernel config, specifically if > > > CONFIG_CGROUP_CPUACCT=y > > > > I do

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:03 PM, Elimar Riesebieter wrote: * Michael Biebl [2018-03-08 18:54 +0100]: [...] Can you check your custom kernel config, specifically if CONFIG_CGROUP_CPUACCT=y I do have CONFIG_CGROUP_CPUACCT=y Well, but why does 237 works with the very same kernel? In my

Bug#892360: systemd: Breaks also all my tested amd64 machines

* Michael Biebl [2018-03-08 18:54 +0100]: [...] > Can you check your custom kernel config, specifically if > CONFIG_CGROUP_CPUACCT=y I do have CONFIG_CGROUP_CPUACCT=y Well, but why does 237 works with the very same kernel? Elimar -- Numeric stability is probably not all

Bug#892360: systemd: Breaks also all my tested amd64 machines

Can you check your custom kernel config, specifically if CONFIG_CGROUP_CPUACCT=y Probably easiest if you just use grep grep CGROUP /boot/config-$(uname -r) Done in another private email. Can copy here: diff config-4.14.0-3-amd64 config-4.14.23 | grep CGROUP < CONFIG_BLK_CGROUP=y < #

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 18:31 schrieb Elimar Riesebieter: > * Michael Biebl [2018-03-08 17:09 +0100]: > >> Am 08.03.2018 um 17:05 schrieb Michael Biebl: >>> Control: tags -1 moreinfo >>> >>> Am 08.03.2018 um 16:23 schrieb valette: >>> > [...] > >> Could you check if >>

Bug#892360: systemd: Breaks also all my tested amd64 machines

* Michael Biebl [2018-03-08 17:09 +0100]: > Am 08.03.2018 um 17:05 schrieb Michael Biebl: > > Control: tags -1 moreinfo > > > > Am 08.03.2018 um 16:23 schrieb valette: > > [...] > Could you check if > https://github.com/systemd/systemd/issues/8387 > looks related > > I.e.

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 17:09 schrieb Michael Biebl: > Could you check if > https://github.com/systemd/systemd/issues/8387 > looks related > > I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem. If not, follow the instructions at

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 17:05 schrieb Michael Biebl: > Control: tags -1 moreinfo > > Am 08.03.2018 um 16:23 schrieb valette: > >> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT) > > Is this also happening with a Debian provided kernel? > I see both you and Elimar use a custom one. > > Is this a

Processed: Re: Bug#892360: systemd: Breaks also all my tested amd64 machines

Processing control commands: > tags -1 moreinfo Bug #892360 [systemd] systemd pid 1 freezes at startup on x86 systems Added tag(s) moreinfo. -- 892360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#892360: systemd: Breaks also all my tested amd64 machines

Control: tags -1 moreinfo Am 08.03.2018 um 16:23 schrieb valette: > Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT) Is this also happening with a Debian provided kernel? I see both you and Elimar use a custom one. Is this a virtualized environment or read hardware? Do you get a coredump? If

Bug#892360: systemd: Breaks also all my tested amd64 machines

Package: systemd Version: 238-1 Followup-For: Bug #892360 I also get a sigsegv on two diferent machines after today upgrade. You can reboot and use sysvinit mode => bug is realy in systemd. Kernel and packages uptodate -- Package-specific info: -- System Information: Debian Release: