It was <2013-12-20 pią 10:42>, when Yang Chengwei wrote: > On Fri, Dec 20, 2013 at 02:47:18AM +0000, Wu, Zhiwen wrote: >> Hi folks, >> I created a minimal bootable image (just with sdb capability) from >> latest repos of devel:wayland:Mobile for our Intel reference >> device. And after boot-up and "sdb shell" to login the root user, I >> found the [email protected] failed at booting. The related log >> from "journalctl" attached here: >> ============================================================================================================== >> [/usr/lib/systemd/system/graphical.target.wants/../[email protected]:15] >> Unknown lvalue 'ControlGroup' in section 'Service' >> [/usr/lib/systemd/system/graphical.target.wants/../[email protected]:16] >> Unknown lvalue 'ControlGroupModify' in section 'Service' >> ============================================================================================================== >> >> If I remove the "ControlGroup" and "ControlGroupModify" entries from >> [email protected], I got these: >> ======================================= >> Starting user-5000.slice. >> Created slice user-5000.slice. >> Starting User Manager for 5000... >> Starting Session c1 of user app. >> Started Session c1 of user app. >> Failed to start Start the av system. >> Unit avsystem.service entered failed state. >> Started Generate environment from /etc/profile.d. >> Starting user-5000.slice. >> Created slice user-5000.slice. >> Starting User Manager for 5000... >> Starting Session c1 of user app. >> Started Session c1 of user app. >> pam_unix(login:session): session opened for user app by (uid=0) >> Failed to create root cgroup hierarchy: Permission denied >> Failed to create root cgroup hierarchy: Permission denied >> Failed to allocate manager object: Permission denied >> Failed to create root cgroup hierarchy: Permission denied >> Failed to create root cgroup hierarchy: Permission denied > > It costs me several hours to debug why systemd user session fail to > start. > > Even I created these cgroups and chmod their files to 777, it less > permission to write, so the "systemd --user" fail with "Permission > denied". > > The workaround so far is add kernel cmdline option "security=none".
What version of systemd do you use? What kernel? If it is mobile kernel and systemd-208 it won't work. New systemd needs some features not present in the mobile kernel. I've back-ported some patches and I will push them to the mobile Please refer to my discussion with Casey. -- Łukasz Stelmach Samsung R&D Institute Poland Samsung Electronics
pgpmEdjiyN3cG.pgp
Description: PGP signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
