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

Alad · 2015-01-22 13:33:43

@Janilson: No, that's definitely not OK and most of us don't have this issue. You probably want to open a new thread (with the necessary detail) for this.

keystroke · 2015-02-17 00:29:41

It may not be harmful, but I too am getting the mismatch and watchdog warnings. I have a feeling this is why fsck runs everytime I boot up.

Narga · 2015-04-07 08:39:21

I had same problem, my laptop hang with msg:

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

Only thing I can do is long press on the power button to make it poweroff. In the next boot, I got a ton of errors msg that scan and fix my HDD. This problem occurred since the beggin of 2013 and I don't find any solution it.

x33a · 2015-04-07 12:40:30

Narga wrote:

I had same problem, my laptop hang with msg:
cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
watchdog watchdog0: watchdog did not stop!
Only thing I can do is long press on the power button to make it poweroff. In the next boot, I got a ton of errors msg that scan and fix my HDD. This problem occurred since the beggin of 2013 and I don't find any solution it.

You have been doing a hard shutdown regularly since 2013?

hoschi · 2015-04-07 14:17:47

Narga wrote:

I had same problem, my laptop hang with msg:
cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
watchdog watchdog0: watchdog did not stop!
Only thing I can do is long press on the power button to make it poweroff. In the next boot, I got a ton of errors msg that scan and fix my HDD. This problem occurred since the beggin of 2013 and I don't find any solution it.

There seems to be no releation to the cgroup-message.
I really wonder how you could ignore such an issue for so long time, at least your filesystem is doing it's job and the various system-shutdown steps seem to work on some degree. You should really care about "hard shutdown", this is reckless and dangerous, a "hard shutdown" is only a worst case exit.

Question to everyone:
Who is using the "systemd" hook in mkinitcpio.conf and who is using the "base" hook in mkinitcpio.conf?

Last edited by hoschi (2015-04-07 14:18:53)

Narga · 2015-04-07 15:39:01

hoschi wrote:

Narga wrote:
I had same problem, my laptop hang with msg:
cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
watchdog watchdog0: watchdog did not stop!
Only thing I can do is long press on the power button to make it poweroff. In the next boot, I got a ton of errors msg that scan and fix my HDD. This problem occurred since the beggin of 2013 and I don't find any solution it.
There seems to be no releation to the cgroup-message.
I really wonder how you could ignore such an issue for so long time, at least your filesystem is doing it's job and the various system-shutdown steps seem to work on some degree. You should really care about "hard shutdown", this is reckless and dangerous, a "hard shutdown" is only a worst case exit.
Question to everyone:
Who is using the "systemd" hook in mkinitcpio.conf and who is using the "base" hook in mkinitcpio.conf?

I known that "hard shutdown" is dangerous but to poweroff my laptop, I must do it.
I'm using "base" hook in mkinitcpio.conf

HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

x33a wrote:

Narga wrote:
I had same problem, my laptop hang with msg:
cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
watchdog watchdog0: watchdog did not stop!
Only thing I can do is long press on the power button to make it poweroff. In the next boot, I got a ton of errors msg that scan and fix my HDD. This problem occurred since the beggin of 2013 and I don't find any solution it.
You have been doing a hard shutdown regularly since 2013?

Yes, sometimes it's work fine for serveral months then it's back again, for example: I got this for 2 month ago but it's not occured for 5 months before.

hoschi · 2015-04-07 16:26:23

After a shutdown failed and you booted the machine again, you could take a look at your systemlog with "journalctl -rb -1" as root.
This will print the log of your last "boot" in reverse order, maybe you can see there an issue. Generally I would recommend you searching help for this in a new thread.

feklee · 2015-04-20 11:02:09

When running "sudo /sbin/reboot" I also get the mismatch error, then a message "reboot: System halted", and then the system hangs. @Narga, did you further investigate the issue, possibly solve it?

Here are the last 10 lines from systemctl up until "-- Reboot --" where the system was hanging, plus the first line after I restarted it:

Apr 20 12:54:13 wiwi systemd[1]: Unset automount EFI System Partition Automount.
Apr 20 12:54:13 wiwi systemd[1]: Starting Unmount All Filesystems.
Apr 20 12:54:13 wiwi systemd[1]: Reached target Unmount All Filesystems.
Apr 20 12:54:13 wiwi systemd[1]: Starting Final Step.
Apr 20 12:54:13 wiwi systemd[1]: Reached target Final Step.
Apr 20 12:54:13 wiwi systemd[1]: Starting Halt...
Apr 20 12:54:13 wiwi systemd[1]: Shutting down.
Apr 20 12:54:14 wiwi systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 20 12:54:14 wiwi systemd-journal[131]: Journal stopped
-- Reboot --
Apr 20 15:00:44 wiwi systemd-journal[150]: Runtime journal is using 8.0M (max allowed 393.1M, trying to leave 589.7M free of 3.8G available → current limit 393.1M).

As you can see, before turning off the machine by long-pressing the power button, then restarting it again, I gave it enough time to reboot by itself: about two hours

(This system, a brand new Thinkpad T550 / Broadwell-U is a nightmare to set up. All over the place, there are things that don't work, graphics, sound, suspend to RAM, mouse buttons, etc. I don't even intend to fix all that. Just I want to get a stable system which can be used for typing LaTeX documents.)

Last edited by feklee (2015-04-20 13:09:33)

Narga · 2015-04-20 15:26:14

I'm still researching about this problem but I'm not find any good solution. Sometimes, I still need hard poweroff by long press the power button.
The temporality method is enable sysrq button to help you shutdown or reboot your system safely, but it's 100% works
To enable it, just use:

echo 1 > /proc/sys/kernel/sysrq

hoschi · 2015-04-22 09:32:55

SYSRQ is the trusted way, since Systemd-219 this should work also by default:

When the user presses Ctrl-Alt-Del more than 7x within 2s an
immediate reboot is triggered. This useful if shutdown is
hung and is unable to complete, to expedite the
operation. Note that this kind of reboot will still unmount
all file systems, and hence should not result in fsck being
run on next reboot.

http://lists.freedesktop.org/archives/s … 28447.html

As Systemd is launched by default from the inital ramdisk I'm afraid this needs a new kernel release from the official repositories from Archlinux, the current ramdisk should still launch the old Systemd-218 binary. This is the problem with an inital ramdisk, complicated to maintain and unnecessary in most cases. Of course you could create a new inital ramdisk with mkinitcpio.

Last edited by hoschi (2015-04-22 09:37:52)

Narga · 2015-04-22 17:31:47

On 4/23/15, I've upgraded to

systemd-219-6

systemd-sysvcompat-219-6

, hopping it fixes this problem.

Last edited by Narga (2015-04-24 00:15:56)

MisterChoc · 2015-10-03 00:14:16

Still having this issue with 226. Nobody found a solution? I've tried @Naga one but it's not working

Last edited by MisterChoc (2015-10-03 12:43:14)

Janilson · 2015-10-03 10:36:09

MisterChoc wrote:

Still having this issue with 223. Nobody found a solution? I've tried @Naga one but it's not working

I still have this problem too
The only way was to use the LTS Kernel (linux-lts), but I don't think it's the best way

MisterChoc · 2015-10-03 13:15:50

@Janilson so yours doesn't turn off at all? I guess hard shutdown could cause some issues. Btw do you have a thinkpad?
I can't explain it but mine does now when I run sudo shutdown -P 0 eventhough I can still see the error message for one second but it doesn't hang anymore.

Janilson · 2015-10-03 15:09:39

@MisterChoc, my PC isn't a Thinkpad, it's a desktop PC. I can only reboot/shutdown it if I'm using LTS Kernel. When I do, I still see that error message but PC doesn't hang. But when I use normal Kernel it freezes and I can't reboot or shutdown it.

I've just rebooted the PC (using LTS Kernel) to use normal kernel and it hangs. There's no error message anymore. It's just freezes and shows the message I see when I boot the PC

....
[   OK  ] Started WPA supplicant.
[   OK  ] Created slice user-120.slice
             Starting User Manager for UID 120
[   OK  ] Started Session c1 of user gdm
[   OK  ] Started User Manager for UID 120

Ocypheum · 2015-10-03 17:50:21

If I understand correctly, the hanging on shutdown is not caused by the cgroup message or the watchdog thing. You should really create a new thread for your specific problem.

MisterChoc · 2015-10-04 17:19:45

@Janilson do you use UEFI or legacy boot? I'm using legacy and I saw a guy who got the same issue and reinstalled using UEFI boot and fixed it that way. Unfortunately since my machine is a production machine and pretty busy atm I won't be able to try that before a few weeks
Edit: try the "poweroff" command. Worked for me shutdown -H 0 would fail... Don't ask me why

Last edited by MisterChoc (2015-10-04 17:45:38)

Narga · 2015-10-06 04:10:29

MisterChoc wrote:

Still having this issue with 226. Nobody found a solution? I've tried @Naga one but it's not working

Have you used any saving power softwares like powertop, tpl ...? I found they are the cause of this problem when I active PCI power saving, if I disable it, my laptop shutdowns correctly with this msg.

fakemoth · 2015-10-06 07:24:25

Hey, just wanted to say I have the same message and my PC doesn't shut down either, see here my thread https://bbs.archlinux.org/viewtopic.php … 8#p1567918 it would be wonderfull if you people can share some insight.

Last edited by fakemoth (2015-10-06 07:39:02)

MisterChoc · 2015-10-06 18:15:47

Narga wrote:

MisterChoc wrote:
Still having this issue with 226. Nobody found a solution? I've tried @Naga one but it's not working
Have you used any saving power softwares like powertop, tpl ...? I found they are the cause of this problem when I active PCI power saving, if I disable it, my laptop shutdowns correctly with this msg.

No I have nothing like that installed.
@fakemoth can you give more info on your setup? I'm trying to find comon stuff on our setup. Especially are you using UEFI or Legacy boot?

fakemoth · 2015-10-07 11:20:25

I am using the legacy boot. BTW I tried with and without all power options, both in packages or in BIOS settings, doesn't seem related. Seems to me more and more (see the link below) like a cryptic systemd bug than none except Poettering will figure out This doesn't seem the proper thread for this discussion, as we will hijack it, let's use mine https://bbs.archlinux.org/viewtopic.php?id=203161

Last edited by fakemoth (2015-10-07 13:25:12)

MisterChoc · 2015-10-07 12:11:06

fakemoth wrote:

I am using the legacy boot. BTW I tried with and without all power options, both in packages or in BIOS settings, doen't seem related. Seems to me more and more (see the link below) like a cryptic systemd bug than none except Poettering will figure out This doesn't seem the proper thread for this discussion, as we will hijack it, let's use mine https://bbs.archlinux.org/viewtopic.php?id=203161

LIke a said some dude fixed it by reinstalling using UEFI, I can't try this atm since I use this machine at work

Arch Linux

#26 2015-01-22 13:33:43

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

#27 2015-02-17 00:29:41

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

#28 2015-04-07 08:39:21

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

#29 2015-04-07 12:40:30

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

#30 2015-04-07 14:17:47

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

#31 2015-04-07 15:39:01

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

#32 2015-04-07 16:26:23

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

#33 2015-04-20 11:02:09

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

#34 2015-04-20 15:26:14

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

#35 2015-04-22 09:32:55

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

#36 2015-04-22 17:31:47

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

#37 2015-10-03 00:14:16

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

#38 2015-10-03 10:36:09

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

#39 2015-10-03 13:15:50

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

#40 2015-10-03 15:09:39

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

#41 2015-10-03 17:50:21

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

#42 2015-10-04 17:19:45

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

#43 2015-10-06 04:10:29

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

#44 2015-10-06 07:24:25

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

#45 2015-10-06 18:15:47

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

#46 2015-10-07 11:20:25

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

#47 2015-10-07 12:11:06

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

Board footer