| Summary: | qemuarm-alt backtrace during boot | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Richard Purdie <richard.purdie> |
| Component: | kernel | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | randy.macleod, tom.zanussi |
| Version: | 3.2 | ||
| Target Milestone: | 3.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2020-09-02 09:06:05 UTC
This and all of the AB-int boot failures all seem to point to qemu not getting enough resources and starving in one way or another. Do we have a way to dump the machine state at the time of failure ? Or do we have a way to pump the priority of the qemu process(es) ? Sakib and I are working on that now, see: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14006 If you have any suggestion about what data to collect, we're all ears. Lowered to medium, raise to M+ if seen again. Not seen in a while. Reopen if you see this issue. |