FS#55826 - [linux] cgroup: group2: unknown option "" in 4.13.3

Attached to Project: Arch Linux
Opened by marcel (donutloop) - Sunday, 01 October 2017, 16:01 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 07 October 2017, 15:47 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

cgroup: group2: unknown option ""

Kernel version:

Linux linux 4.13.3-1-ARCH #1 SMP PREEMPT Thu Sep 21 20:33:16 CEST 2017 x86_64 GNU/Linux

After I updated my kernel.This pops up every time I do shut down or restart my laptop during the black screen with white text stuff and freeze the whole process


This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 07 October 2017, 15:47 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#54746 
Comment by loqs (loqs) - Sunday, 01 October 2017, 17:42 GMT
Can you try with the boot option systemd.legacy_systemd_cgroup_controller or systemctl mask mkinitcpio-generate-shutdown-ramfs.service
If those methods both prevent the error from being shown then I would suspect the issue is 4.13's version of
https://bbs.archlinux.org/viewtopic.php?id=227974 and a duplicate of  FS#54746  see also https://bbs.archlinux.org/viewtopic.php?id=230435
Comment by marcel (donutloop) - Monday, 02 October 2017, 18:26 GMT
I did have tried out "systemctl mask mkinitcpio-generate-shutdown-ramfs.service". The error message doesn't pop up anymore but still, my laptop can't properly shutdown (frozen in the step).
I have a "Lenovo ThinkPad P50". Shall I execute a command to get more log information?
Comment by loqs (loqs) - Monday, 02 October 2017, 18:55 GMT
Would suggest you start a thread on the forums and provide the journal entries from an attempted shutdown.
Comment by Paweł Tomkiel (neonkowy) - Wednesday, 04 October 2017, 11:54 GMT
I'm experiencing this warning (error?) as well, but in my case shutdown isn't freezing. Dell Latitude E5470
Comment by loqs (loqs) - Wednesday, 04 October 2017, 16:32 GMT
@neonkowy see the links in my first comment
Comment by marcel (donutloop) - Friday, 06 October 2017, 16:14 GMT
How can I get logs of the last shutdown?
Comment by loqs (loqs) - Friday, 06 October 2017, 17:31 GMT Comment by Adam (breskov) - Friday, 06 October 2017, 21:20 GMT
I have the same issue, and i cannot find any solution! Please report if you have something about this problem!
Comment by loqs (loqs) - Friday, 06 October 2017, 23:17 GMT
@breskov which issue the display of the message cgroup: group2: unknown option or the system not shutting down or rebooting?
The former I already covered in my first comment and there is no information on the latter issue.
The latter may well have been fixed already with linux 4.13.5-1 but without more information is required.
Comment by marcel (donutloop) - Saturday, 07 October 2017, 08:18 GMT
Start

Command:

journalctl -b -p err

Result:
Oct 07 10:12:28 linux kernel: DMAR: DRHD: handling fault status reg 3
Oct 07 10:12:28 linux kernel: DMAR: [DMA Read] Request device [00:12.4] fault addr 57fff000 [fault reason 02] Present bit in context entry is clear
Oct 07 10:12:28 linux gnome-session-binary[452]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 07 10:12:32 linux kernel: tpm tpm0: Operation Timed out
Oct 07 10:12:32 linux kernel: tpm tpm0: TPM self test failed
Oct 07 10:12:44 linux kernel: mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not reg notif event ret=-22
Comment by marcel (donutloop) - Saturday, 07 October 2017, 08:23 GMT


Command:

journalctl -b -1 -p err


Result:

Oct 06 18:04:37 linux kernel: DMAR: DRHD: handling fault status reg 3
Oct 06 18:04:37 linux kernel: DMAR: [DMA Read] Request device [00:12.4] fault addr 57fff000 [fault reason 02] Present bit in context entry is clear
Oct 06 18:04:37 linux gnome-session-binary[445]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 06 18:04:41 linux kernel: tpm tpm0: Operation Timed out
Oct 06 18:04:41 linux kernel: tpm tpm0: TPM self test failed
Oct 06 18:04:50 linux ntpd[366]: bind(28) AF_INET6 2003:ca:53cd:dc00:3f86:f747:afa3:e816#123 flags 0x11 failed: Cannot assign requested address
Oct 06 18:04:50 linux ntpd[366]: unable to create socket on wlp4s0 (9) for 2003:ca:53cd:dc00:3f86:f747:afa3:e816#123
Oct 06 18:04:53 linux kernel: mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not reg notif event ret=-22
Oct 07 04:12:21 linux ntpd[366]: bind(29) AF_INET6 fd00::2e5e:d26:2231:5149#123 flags 0x11 failed: Cannot assign requested address
Oct 07 04:12:21 linux ntpd[366]: unable to create socket on wlp4s0 (11) for fd00::2e5e:d26:2231:5149#123
Oct 07 10:10:09 linux gdm[365]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Oct 07 10:10:09 linux gdm[365]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Oct 07 10:10:09 linux gdm[365]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Oct 07 10:11:39 linux kernel: wlp4s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
Oct 07 10:11:39 linux kernel: wlp4s0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-22)
Comment by loqs (loqs) - Saturday, 07 October 2017, 08:43 GMT Comment by marcel (donutloop) - Saturday, 07 October 2017, 09:54 GMT
Thanks for your help, I have learned a lot!
Comment by Adam (breskov) - Saturday, 07 October 2017, 10:56 GMT
I had the cgroup: group2: unknown option "" message, and I was unable to shutdown or reboot my system.

I also had these messages:

DMAR: DRHD: handling fault status reg 3
wlp4s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

But fortunately intel_iommu=off worked well for me too.

Thank you very much loqus!
Comment by Johannes M. Seifert (Jormsen) - Saturday, 07 October 2017, 13:01 GMT
same problem for me,
masking mkinitcpio-generate-shutdown-ramfs.service helped for the cgroup2 error, but my notebook didn't turn of though.
What solved the power-off-problem was an update to 4.13.5-1-ARCH (it's in testing)

Loading...