Bug 7387

Summary: qemux86-64 core-image-sato-sdk has opcode errors in logs during sanity tests
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Beth Flanagan <elizabeth.flanagan>
Component: deploymentAssignee: Richard Purdie <richard.purdie>
Status: VERIFIED FIXED QA Contact: Mihail Stanciu <stanciux.mihail>
Severity: normal    
Priority: Medium+ CC: alexandru.c.georgescu
Version: unspecified   
Target Milestone: 1.8 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Beth Flanagan 2015-03-03 19:43:59 UTC 
from:

https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/217/steps/Running%20Sanity%20Tests/logs/stdio

| [   42.027846] Write protecting the kernel read-only data: 14336k
| [   42.033837] Freeing unused kernel memory: 1172K (ffff8800018db000 - ffff880001a00000)
| [   42.035402] Freeing unused kernel memory: 352K (ffff880001da8000 - ffff880001e00000)
| ***********************
| Central error: [   34.784887] hda: possibly failed opcode: 0xea
| ***********************
| [    4.702789] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO0
| [    4.702883] hdc: MWDMA2 mode selected
| [    4.703677] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Comment 2 Alexandru Georgescu 2015-03-26 06:22:22 UTC 
Mihai, can you verify during m4.rc1 testing?
Comment 3 Mihail Stanciu 2015-03-31 14:00:41 UTC 
Sanity tests were all green on M4 RC1.
Marking as verified.