Bug 11685

Summary: qemumips64 testimage hangs at devtmpfs: mounted
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Armin Kuster <akuster>
Component: coreAssignee: 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
Not sure if this is an new issue or one that was being masked by the console issue.
Comment 1 Armin Kuster 2017-06-19 15:30:52 UTC
looks like the later kernel introduced this behavior.
Comment 2 Armin Kuster 2017-06-20 02:23:06 UTC
This appears to be cause by the console fix that addressed the x11 issue on qemumips64
Comment 3 Armin Kuster 2017-06-20 04:45:55 UTC
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
Comment 4 Armin Kuster 2017-06-20 20:23:07 UTC
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.
Comment 5 Randy MacLeod 2017-06-22 14:56:22 UTC
Armin, Do you want to close this defect and open separate defects for the new problem(s) that you have found?
Comment 6 Armin Kuster 2017-06-22 16:24:25 UTC
(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.
Comment 7 Armin Kuster 2017-06-22 16:24:54 UTC
issue fixed by posted commit.