* 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 from within systemd
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
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 wi
* 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 have CONFIG_CGROUP_CPUACCT=y
> >
> > We
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 case it is not set,
* 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 that
important wh
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
< # CONFIG_
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
>> https://github.com/systemd/system
* 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. if booting with syst
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
https://freedesktop.org/wiki/Software/systemd/Debug
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 vir
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
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: buster/sid
13 matches
Mail list logo
