Description of problem: When starting on a fresh installation of Mageia X86 on real hardware, there is the message: "Failed to get cgroup : no media found Starting version 229" After updates, same message plus a message of systemd unable to load a legacy module Version-Release number of selected component (if applicable): Installation done with an usb key prepared with isodumper. MB Asus M4A89TD PRO/USB3.0 AMD Phenom II X2 550 IOMMU activated Nota: the RD990 IOMMU is list as unknown in HardDrake (it's the same in MGA5 on this hardware and no problem at all) How reproducible: Allways Steps to Reproduce: 1. 2. 3.
(The reporter saw this on an install from DVD X86_64 KDE) I was sure I had often seen the same "failed to get cgroup" error, but cannot find it in my logs. Maybe it got fixed here before I last vacuumed my logs, or it was on another system ... I'll check that one. @ Philippe about: > a message of systemd unable to load a legacy module that message can be ignored, it doesn't harm and we all see it since we switched to systemd
CC: (none) => marja11Component: Installer => RPM PackagesAssignee: bugsquad => mageiaSource RPM: DVD X86_64 KDE => systemd
I haven't found the "Failed to get cgroup" message in logs, perhaps because it appears at the very beginning.
*** Bug 18391 has been marked as a duplicate of this bug. ***
CC: (none) => westel
(In reply to Philippe Flat from comment #2) > I haven't found the "Failed to get cgroup" message in logs, perhaps because > it appears at the very beginning. You're right, after seeing the message, it doesn't show up in my logs, either.
Hello, I see also this message on each Mageia 6 installation. Failed to get cgroup : no media found
CC: (none) => yves.brungard_mageia
From #mageia-dev, times are CEST: 2016:05:22:10:57 < NyB> btw, that "failed to get cgroup: ..." message on boot comes from here: https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L1722 2016:05:22:10:57 < [mbot> [ systemd/udevd.c at master · systemd/systemd · GitHub ] 2016:05:22:11:01 < NyB> it's interesting that the messaged does not appear to be logged anywhere 2016:05:22:11:07 < NyB> ah, here's the fix: https://github.com/systemd/systemd/commit/6d2353394fc33e923d1ab464c8f88df2a5105ffb 2016:05:22:11:07 < [mbot> [ udev: fix cg_unified() return code checking · systemd/systemd@6d23533 · GitHub ] so it got fixed upstream and the fix only needs to land in Mageia :-)
Keywords: (none) => UPSTREAMURL: (none) => https://github.com/systemd/systemd/issues/2635
URL: https://github.com/systemd/systemd/issues/2635 => (none)See Also: (none) => https://github.com/systemd/systemd/issues/2635
Keywords: (none) => PATCH
This is now in svn with system v230. I'll ask for push
With the new systemd , there is no more the message for cgroup. Only remains Fail to start Load Legacy module configuration. Dmesg extract: 7.249613] acpi-cpufreq: overriding BIOS provided _PSD data [ 7.326989] systemd[1]: fedora-loadmodules.service: Main process exited, code=exited, status=1/FAILURE [ 7.327129] systemd[1]: Failed to start Load legacy module configuration. [ 7.327184] systemd[1]: fedora-loadmodules.service: Unit entered failed state. [ 7.327201] audit: type=1130 audit(1465407332.943:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fedora-loadmodules comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' [ 7.327210] systemd[1]: fedora-loadmodules.service: Failed with result 'exit-code'. [ 7.657499] systemd[1]: Started Journal Service. Thanks for the work done
As I haven't anymore the problem, I consider this bug as solved.
Status: NEW => RESOLVEDResolution: (none) => FIXED