| Summary: | qemumips64 testimage hangs at devtmpfs: mounted | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Armin Kuster <akuster> |
| Component: | core | Assignee: | Armin Kuster <akuster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, randy.macleod |
| Version: | 2.2.3 | ||
| Target Milestone: | 2.2.3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Armin Kuster
2017-06-19 03:17:21 UTC
looks like the later kernel introduced this behavior. This appears to be cause by the console fix that addressed the x11 issue on qemumips64 Watson, the clues are in the commit. "IOW, if you boot with console=ttyS0 console=tty0 then all kernels prior to this commit will produce output on both ttyS0 and tty0 but input will only be taken from tty0. With this patch the serial console will always be the primary console instead of tty0, potentially preventing people from getting into their machines in emergency situations." runqemu qemumip64 still boots when the qemu append console line is changed to "console=tty0" testimage runs when oeqa's runqemu.py console append is changed as well. Are we seeing this on pyro or Master on 4.9 or 4.10 kernels? I should have patches tomorrow after a few tests on other arches http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=akuster/morty-next&id=f137672e08fbd63d7e3de87b33cd3131a1cc00c3 fixed this issue. but now there is new mips issue with lsb. Armin, Do you want to close this defect and open separate defects for the new problem(s) that you have found? (In reply to comment #5) > Armin, Do you want to close this defect and open separate defects for the > new problem(s) that you have found? sure. issue fixed by posted commit. |