| Summary: | systemd failed proc-sys-fs-binfmt_misc.mount service | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexandru Palalau <alexandrux.palalau> |
| Component: | core | Assignee: | Ross Burton <ross.burton> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, sgw |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M5 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
systemctl should be able to give you the log from starting that service that failed. Maybe that kernel doesn't have binfmt_misc support? Assigning to Radu for the next step of debugging. Some of the qemu machines were not recommending kernel-modules, so they didn't have the binfmt-misc modules installed. Patch sent. That patch rejected. Second patch almost send and then self-rejected. Patch three sent! Merged as oe-core d42f7fc333495dc35227a6d1027492ab70f29b23 Verified on master branch. Commit ID: 4d8ab87d25ea6e59dc88375813ef88ee0ac813d0. |
BUILD: 1.5_M3: 3dee534f1e25109e0bdb681de0746c336f4b8840 ENVIRONMENT: Fedora 17 STEPS TO REPRODUCE: 1. Prepare a core-image-sato image with systemd support and launch it. Refer to TC-549 in order how to build it. 2. List all the failed services by running the following command: $ systemctl --failed No failed services at this point 3. Check df output Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 364843 283494 62806 82% / devtmpfs 56700 4 56696 0% /dev tmpfs 58584 0 58584 0% /dev/shm tmpfs 58584 2264 56320 4% /run tmpfs 58584 0 58584 0% /sys/fs/cgroup df: /proc/sys/fs/binfmt_misc: No such device tmpfs 58584 16 58568 0% /tmp tmpfs 58584 92 58492 0% /var/volatile 4. List all the failed services by running the following command: $ systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.mount loaded failed failed Arbitrary Executable File Formats File System LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.