Bug 14010 - qemumips-alt systemd boot unit failure on fedora32-ty-1
Summary: qemumips-alt systemd boot unit failure on fedora32-ty-1
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 3.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 3.4 M1
Assignee: akuster
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2020-08-14 15:38 UTC by Richard Purdie
Modified: 2021-05-06 15:13 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Log from failure (1.47 MB, application/octet-stream)
2020-08-14 15:38 UTC, Richard Purdie 		no flags Details
systemd message (87.95 KB, text/plain)
2020-09-10 21:43 UTC, akuster 		akuster808: copyright-waived+
Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Purdie 2020-08-14 15:38:10 UTC 
Created attachment 4715 [details]
Log from failure

https://autobuilder.yoctoproject.org/typhoon/#/builders/102/builds/811

The systemd-hostnamed unit fails, full testimage log attached, grep for "Failed to run event loop".
Comment 1 akuster 2020-09-10 21:41:56 UTC 
This looks like a dup.

I did have a different systemd-error after updating to with rniece changes.

I think I over burdened my system. 

1) I ran:
bitbake core-image-full-cmdline core-image-sato core-image-sato-sdk

using all cpus

2) on a different poky location.

bitbake core-image-full-cmdline core-image-sato core-image-sato-sdk -c testimage.

It generated this dump.
Comment 2 akuster 2020-09-10 21:43:47 UTC 
Created attachment 4721 [details]
systemd message
Comment 3 Randy MacLeod 2021-05-06 15:13:33 UTC 
Not seen since the page table code changes and moving the rootfs to tmpfs.