cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

hoschi · 2013-12-30 16:02:51

Hello!

I've installed Archlinux a new ThinkPad X220 and get this message during shutdown/reboot

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

What does want Systemd tell me?

I've never seen this on my other systems (ThinkPad t430s and ThinkCenter M).

Somebody mentioned it here and posted also a screenshot:
https://bbs.archlinux.org/viewtopic.php?pid=1362098

The discussion there doesn't take a good direction and I care only about this message, no problem with a "delay" or something similiar.

Thank you

graysky · 2014-01-18 22:22:40

I get the same message on power down or reboot. No answer to the question though. Does yours also report:

watchdog watchdog0: watchdog did not stop!

clfarron4 · 2014-01-18 23:12:47

I get both what @hoschi and @graysky posted randomly.

brain0 · 2014-01-19 09:20:08

Okay, here's a rather long explanation of some of the things that happen during shutdown (simplified at some places, because some details don't help the understanding at all).

systemd activates shutdown.target, which conflicts with all services and mount points, essentially stopping everything that was started.
Activating shutdown.target starts a service that creates the executable /run/initramfs/shutdown, if it doesn't exist yet (more on that further down).
Upon reaching shutdown.target, systemd replaces itself with /usr/lib/systemd/systemd-shutdown.
systemd-shutdown tries kill all remaining processes, unmount all remaining file systems, detach all loop and device-mapper devices. It gives up at some point, since most of the time it will fail for a few mount points.
If /run/systemd/shutdown does not exist, systemd-shutdown proceeds to power off or reboot the machine.
systemd-shutdown changes the root to /run/initramfs, puts the old root to /oldroot and replaces itself with /shutdown.
In our case, /shutdown is a copy of /usr/lib/systemd/systemd-shutdown, which again tries to unmount everything and so on. Most of the time, it succeeds now (this means that the root file system is not only remounted read-only as it was classically done, but unmounted entirely. Any encryption mapping is also closed, which causes the kernel to wipe the encryption key from memory, to prevent a cold boot attack).
/shutdown then proceeds to power off or reboot.

So, how does the hardware watchdog come into play here? By default, systemd sets the watchdog timer to 10 minutes before it replaces itself with systemd-shutdown. Then it closes it, but does not stop it. When systemd-shutdown takes over, it opens the watchdog again. The same happens again when systemd-shutdown switches to /run/initramfs. This has a very useful result: If somehow the execution of the new binary fails, the hardware watchdog will time out after 10 minutes and reboot the computer - so your machine reboots instead of hanging indefinitely. The downside: You get a "watchdog did not stop" warning twice during shutdown.

As for the other error:

cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"

This is a message from the kernel that is generated when a cgroup file system is remounted and options are changed that should not be changed. I cannot explain this entirely, but somehow this seems to happen while /oldroot/sys/fs/cgroup/systemd is being unmounted. In any case, it is of no special interest.

graysky · 2014-01-19 10:11:22

Thanks for the detailed explanation. I added a link to the wiki.

hoschi · 2014-01-26 15:50:47

Thanks for your detailed explaination brain0! That also explains some random sights of the watchdog during critical shutdowns (e.g. unexpected network outage).

...and options are changed that should not be changed

I don't like this kind of undefined behaviour in technical systems and it makes me a little bit worried. But your honest and clear comment is a lot of better than the typical "ignore that" answer!

ubunchu · 2014-01-28 20:02:36

Stupid question incoming: do we need "watchdog"?
https://wiki.archlinux.org/index.php/Po … I_watchdog
Or is it recommended to leave it as it is?

brain0 · 2014-01-29 12:52:45

ubunchu wrote:

Stupid question incoming: do we need "watchdog"?
https://wiki.archlinux.org/index.php/Po … I_watchdog
Or is it recommended to leave it as it is?

The NMI watchdog is entirely unrelated to this, it's not a "watchdog" in this sense.

bdantas · 2014-06-30 14:53:40

So, has anyone found a way to make this error at reboot/shutdown go away?

cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"

I recently starting seeing it and it's quite aggravating.

Last edited by bdantas (2014-06-30 14:55:31)

anatolik · 2014-06-30 15:27:22

bdantas wrote:

So, has anyone found a way to make this error at reboot/shutdown go away?
cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"

This warning comes from kernel/cgroup.c kernel code:

        /* Don't allow flags or name to change at remount */
        if (((opts.flags ^ root->flags) & CGRP_ROOT_OPTION_MASK) ||
            (opts.name && strcmp(opts.name, root->name))) {
                pr_err("option or name mismatch, new: 0x%x \"%s\", old: 0x%x \"%s\"\n",
                       opts.flags & CGRP_ROOT_OPTION_MASK, opts.name ?: "",
                       root->flags & CGRP_ROOT_OPTION_MASK, root->name);
                ret = -EINVAL;
                goto out_unlock;
        }

Thus something tries to remount cgroups with different name and kernel does not like it.

bdantas · 2014-06-30 15:31:53

Best option seems to be to ensure that cgroups is remounted with the same name as before (0x4 systemd) so that the kernel isn't upset about a mismatch. Is there a systemd setting that I can change to accomplish this?

If not, is it possible to turn off the error reporting (by disabling the code you quoted above) without having to recompile the kernel?

Last edited by bdantas (2014-06-30 16:11:49)

clfarron4 · 2014-06-30 16:33:36

Just chiming in here: I get with the linux-ck and linux-lqx packages since BFQ v7r5, not with [core]. Not sure about linux-lts-ck.

I'm not particularly worried though.

calin_ionut · 2014-07-04 07:48:52

I have the same errors on reboot or shutdown:

cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
watchdog watchdog0: watchdog did not stop!

How to fix this?

varikonniemi · 2014-11-29 22:45:47

I first saw this cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd" error today when i upgraded (and got systemd217 among others).

Last edited by varikonniemi (2014-11-29 22:52:45)

clfarron4 · 2014-11-30 11:22:35

@calin_ionut and @varikonniemi: You've read this post (coincidentally in this thread), right?

fabrydrunk · 2015-01-13 12:35:56

Hi guys. I've been facing this problem since 6 months, and I didn't find a solution yet (I even reinstalled the whole archlinux, uselessly).

During shutdown/reboot I always read this lines:

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"
shutdown[1]: Failed to finalize  file systems, ignoring

I read the whole post repeatedly, especially this one, but IF there was a solution to my problem, I unfortunately didn't find it.
Can you tell me how to fix it?

clfarron4 · 2015-01-13 13:03:04

fabrydrunk wrote:

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

The consensus of this thread is that this bit is fine and doesn't seem to be causing anyone anyone any harm.

fabrydrunk wrote:

shutdown[1]: Failed to finalize  file systems, ignoring

This, I've never seen before and is probably one to be looking at.

fabrydrunk · 2015-01-13 14:00:01

So I was looking for a solution that has never been here. Should I write a new thread for my specific problem then?

clfarron4 · 2015-01-13 14:35:40

fabrydrunk wrote:

So I was looking for a solution that has never been here. Should I write a new thread for my specific problem then?

For the second of the two messages, if you want to pursue the message further.

orschiro · 2015-01-13 19:34:19

doesn't seem to be causing anyone anyone any harm.

fabrydrunk wrote:

So I was looking for a solution that has never been here. Should I write a new thread for my specific problem then?

You didn't say whether you experience any negative side effects apart from having that warning displayed.

Last edited by orschiro (2015-01-13 19:34:38)

Jristz · 2015-01-14 23:39:33

orschiro wrote:

doesn't seem to be causing anyone anyone any harm.
fabrydrunk wrote:
So I was looking for a solution that has never been here. Should I write a new thread for my specific problem then?
You didn't say whether you experience any negative side effects apart from having that warning displayed.

and? there is a necesity to be harmfull to find a solution? there is need to have side efects to need to be researched?

I thing if someone want know how supress or remove this message, that is enought to try find a solution... so...

I heard that the problem is how mkinitcpio shutdown work.
You try to use a different mkinitcpio tool? like... dracut? and look if the message persist

orschiro · 2015-01-15 07:50:31

and? there is a necesity to be harmfull to find a solution? there is need to have side efects to need to be researched?

No, but time invested into a message that does not cause any harm can be used more wisely for investigating more serious issues. That's all I wanted to say.

mshan · 2015-01-20 03:05:35

I also have the same

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"
reboot: shut down

at shutdown/reboot.
no solution here yet.
waiting for someone with solution to post here...

Leonid.I · 2015-01-20 22:44:54

Guys, you need to understand that the linux kernel is written by people. So, someone _decided_ that this message should be an error and hence be printed to stdout, while in reality it should have been a warning. There is ton of such places in kernel with "misplaced" log priority (for example, the driver responsible for my kingmax usb flash drive prints an error every time the drive is plugged in, while using other drives results in an info-type identical message).

So, a practical approach would be to submit a bugreport to kernel.org. However, it will most likely be ignored because noone really cares, and neither should you...

On this bright note, can this thread die already?

Janilson · 2015-01-22 12:51:38

Well, I am experiencing this problem, but it's not the error message that bothers me. When I shutdow/reboot my system, my PC hangs. I can only boot it if I manually turn it off (hard way) and turn it on again.

So, is this ok? Is everybody having this issue and it is normal to not be able to turn the computer off only by using shutdown/reboot command or through desktop enviroment?

Sorry to reply to this thread, I think it's the right way.

Arch Linux

#1 2013-12-30 16:02:51

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#2 2014-01-18 22:22:40

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#3 2014-01-18 23:12:47

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#4 2014-01-19 09:20:08

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#5 2014-01-19 10:11:22

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#6 2014-01-26 15:50:47

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#7 2014-01-28 20:02:36

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#8 2014-01-29 12:52:45

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#9 2014-06-30 14:53:40

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#10 2014-06-30 15:27:22

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#11 2014-06-30 15:31:53

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#12 2014-06-30 16:33:36

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#13 2014-07-04 07:48:52

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#14 2014-11-29 22:45:47

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#15 2014-11-30 11:22:35

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#16 2015-01-13 12:35:56

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#17 2015-01-13 13:03:04

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#18 2015-01-13 14:00:01

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#19 2015-01-13 14:35:40

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#20 2015-01-13 19:34:19

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#21 2015-01-14 23:39:33

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#22 2015-01-15 07:50:31

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#23 2015-01-20 03:05:35

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#24 2015-01-20 22:44:54

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

#25 2015-01-22 12:51:38

Re: cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

Board footer