System doesn't reboot/shutdown (cgroup : option or name mismatch....)

clfarron4 · 2015-02-12 16:51:02

gregorylock wrote:

When one needs to do a force shutdown does it hurt the Linux OS like it can Hurt the Windows OS?

In my experience, you're more likely to be able to try and fix it if something does go wrong when you do a hard reset from the hardware in Linux than you are with Windows.

As for breakage? It depends.

gregorylock · 2015-02-13 04:11:47

clfarron4 wrote:

gregorylock wrote:
When one needs to do a force shutdown does it hurt the Linux OS like it can Hurt the Windows OS?
In my experience, you're more likely to be able to try and fix it if something does go wrong when you do a hard reset from the hardware in Linux than you are with Windows.
As for breakage? It depends.

Thank you for the comment. As for the problem we are having, I think that Linux is getting everything terminated, but something is going wrong right at the very end. Since it sounds like it powers off the hard drives. I don't think doing a force shut down is going to break our systems. Personally I've been having it freeze up during a shut down for months. And yet as soon as I turn my computer back on, everything seems to be fine.

* As stated earlier in this thread, sometimes the computer will turn off and sometimes it won't. But this issue has been going on for months and yet doing a force shutdown doesn't seem to break anything.

analca3 · 2015-02-18 13:59:54

Hi! A friend has this issue too... My laptop shows this message and shutdown properly but his one no... Anyone found the solution?

Thank you!

Regards!

sliposk · 2015-02-19 03:20:02

I have a Lenovo B570, I was able to fix this problem by blacklisting acer_wmi .
I dont know if it will work for you, but it solved my problem.
Good Luck.

Last edited by sliposk (2015-02-19 03:22:04)

Janilson · 2015-02-22 15:41:44

sliposk wrote:

I have a Lenovo B570, I was able to fix this problem by blacklisting acer_wmi .
I dont know if it will work for you, but it solved my problem.
Good Luck.

How did you find out that this "acer_wmi" was the problem?
I use a desktop, how could I find something like that and then blacklist it?

Last edited by Janilson (2015-02-22 15:42:17)

sliposk · 2015-02-22 17:44:29

You have alot of reading to do. https://wiki.archlinux.org/index.php/kernel_modules

analca3 · 2015-02-23 17:46:53

Blacklisting acer_wmi not fix our problem , thanks for the reply sliposk.

I have opened a new thread with our specific problem https://bbs.archlinux.org/viewtopic.php?id=194059 , hope anyone can help us .

Regards!

gregorylock · 2015-02-28 04:24:56

I wanted to come on here and just write a quick comment. For some reason my Computer has been shutting down fine. I wish I knew why it's been working right lately.

Soukyuu · 2015-03-17 12:46:03

And for some reason mine started showing this message - yesterday it also refused to turn itself off automatically out of the blue.
I suspect it might have something to do with group/gshadow files, because that's what I last changed in my system files.

There was an update which I merged with etc-update, maybe something went wrong there?

group:

root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root,azure
lp:x:7:daemon,azure
mem:x:8:
kmem:x:9:
wheel:x:10:root,azure
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:
video:x:91:
audio:x:92:
optical:x:93:
floppy:x:94:
storage:x:95:
scanner:x:96:
input:x:97:
power:x:98:
nobody:x:99:
users:x:100:
systemd-journal:x:190:
systemd-journal-gateway:x:191:
systemd-timesync:x:192:
systemd-network:x:193:
systemd-bus-proxy:x:194:
systemd-resolve:x:195:
systemd-journal-upload:x:998:
systemd-journal-remote:x:999:
azure:x:1000:
nvidia-persistenced:x:143:
polkitd:x:102:
avahi:x:84:
mysql:x:89:
kdm:x:135:
colord:x:124:
git:x:997:
rtkit:x:133:
lxdm:x:121:
proc:x:26:

gshadow

root:::root
bin:::root,bin,daemon
daemon:::root,bin,daemon
sys:::root,bin
adm:::root,daemon
tty:::
disk:::root,azure
lp:::daemon,azure
mem:::
kmem:::
wheel:::root,azure
ftp:::
mail:::
uucp:::
log:::root
utmp:x::
locate:::
rfkill:x::
smmsp:::
proc:::
http:::
games:::
lock:::
uuidd:x::
dbus:x::
network:x::
video:x::
audio:::
optical:::
floppy:x::
storage:x::
scanner:x::
input:x::
power:x::
nobody:::
users:::
systemd-journal:::
systemd-journal-gateway:::
systemd-timesync:::
systemd-network:::
systemd-bus-proxy:::
systemd-resolve:::
systemd-journal-upload:!!::
systemd-journal-remote:!!::
azure:!::
nvidia-persistenced:!::
polkitd:!::
avahi:!::
mysql:!::
kdm:!::
colord:!::
git:!::
rtkit:!::
lxdm:!::

matrs · 2015-03-23 19:29:18

Janilson wrote:

Hi all.
I can't reboot or shutdown my computer by command (reboot/shutdown) or by desktop enviroment (Gnome). After 'everything' is done to shutdown I got the "error message"
cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

My system shows the same message and it had the same problem, i looked and i found this kernel bug related to my specific hardware . The thing is that now I can shutdown my system but the message still appears. In my case the problem with the shutdown was related to the use of certain usb ports and a new usb keyboard.

restore · 2015-03-26 10:31:44

I have a similar problem, but my computer hangs *only* when I shutdown. This problem occurs since last week, and now it is also not possible to turn the PC on with pressing 'ESC' key as before. I turned during boot the kernel level to 'debug', and here is the output of

journalctl -b -1

http://tny.cz/f666a4b8

firekage · 2015-03-26 12:34:25

I have the same thing for a long time but it does not do something bad to my desktop machine, can reboot and shutdown as fast at it can be done.

restore · 2015-03-26 23:18:52

I upgraded the UEFI Version of my motherboard. The errormessage still appears, but it's now possible to shutdown again without pressing the power button. So for me --> problem [solved]

Trashlord · 2016-03-15 09:19:31

I've had the same problem for a few days now. I think it's related to USB.

I just managed to shutdown successfully by unmounting my external USB harddrive, then:

# rmmod xhci_pci && shutdown -h now

Shutdown within 3 seconds, no errors.

Arch Linux

#26 2015-02-12 16:51:02

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#27 2015-02-13 04:11:47

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#28 2015-02-18 13:59:54

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#29 2015-02-19 03:20:02

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#30 2015-02-22 15:41:44

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#31 2015-02-22 17:44:29

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#32 2015-02-23 17:46:53

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#33 2015-02-28 04:24:56

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#34 2015-03-17 12:46:03

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#35 2015-03-23 19:29:18

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#36 2015-03-26 10:31:44

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#37 2015-03-26 12:34:25

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#38 2015-03-26 23:18:52

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

#39 2016-03-15 09:19:31

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Board footer