Visible to Intel only — GUID: rnv1487904470061
Ixiasoft
2.3.1. Root Port Legacy Interrupt Status register INTx is stuck HIGH
2.3.2. TLP Bypass Error Status Register may Report Receiver Errors
2.3.3. PCIe CV and PTC Tests in the PCI-SIG Compliance Test Suite may Fail
2.3.4. Returning Incorrect Function Number
2.3.5. Incorrect Return Value for Power Management Register
2.3.6. Register Implementation while using the SR-IOV Feature
2.3.7. Register Implementation while using the Multi-function Feature
2.3.8. Unsuccessful TX Equalization
2.3.9. Link Does Not Degrade With Corrupt Lanes
2.3.10. Warm Reset or PERST Assertion Clears the Sticky Registers
3.1. 843819: Memory Locations May be Accessed Speculatively Due to Instruction Fetches When HCR.VM is Set
3.2. 845719: A Load May Read Incorrect Data
3.3. 855871: ETM Does Not Report IDLE State When Disabled Using OSLOCK
3.4. 855872: A Store-Exclusive Instruction May Pass When it Should Fail
3.5. 711668: Configuration Extension Register Has Wrong Value Status
3.6. 720107: Periodic Synchronization Can Be Delayed and Cause Overflow
3.7. 855873: An Eviction Might Overtake a Cache Clean Operation
3.8. 853172: ETM May Assert AFREADY Before All Data Has Been Output
3.9. 836870: Non-Allocating Reads May Prevent a Store Exclusive From Passing
3.10. 836919: Write of the JMCR in EL0 Does Not Generate an UNDEFINED Exception
3.11. 845819: Instruction Sequences Containing AES Instructions May Produce Incorrect Results
3.12. 851672: ETM May Trace an Incorrect Exception Address
3.13. 851871: ETM May Lose Counter Events While Entering WFx Mode
3.14. 852071: Direct Branch Instructions Executed Before a Trace Flush May be Output in an Atom Packet After Flush Acknowledgment
3.15. 852521: A64 Unconditional Branch May Jump to Incorrect Address
3.16. 855827: PMU Counter Values May Be Inaccurate When Monitoring Certain Events
3.17. 855829: Reads of PMEVCNTR<n> are not Masked by HDCR.HPMN
3.18. 855830: Loads of Mismatched Size May not be Single-Copy Atomic
Visible to Intel only — GUID: rnv1487904470061
Ixiasoft
3.10. 836919: Write of the JMCR in EL0 Does Not Generate an UNDEFINED Exception
Description
When EL0 is using AArch32 register width and a write is performed in EL0 to the Arm* Jazelle® Main Configuration Register (JMCR), the write should be UNDEFINED. Because of this erratum, the write is permitted but ignored.
The erratum occurs under the following conditions:
- The processor is executing in AArch32 user mode.
- A write to the JMCR is executed, using the instruction MCR p14,7,<Rt>,c2,c0,0.
Impact
Rather than treating the MCR instruction as UNDEFINED, a write to the JMCR is ignored.
Workaround
No available workaround.