Mobile 3rd Generation Intel® Core™ Processor Family Specification Update September 2013 Revision 015 Reference Number: 326770
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
Contents Contents Revision History ...............................................................................................................5 Preface ..............................................................................................................................6 Summary Tables of Changes ..........................................................................................8 Identification Information ..................................................................................
Contents 4 Specification Update
Revision History Revision Description Date 001 • Initial Release.
Preface This document is an update to the specifications contained in the Affected Documents table below. This document is a compilation of device and documentation errata, specification clarifications and changes. It is intended for hardware system manufacturers and software developers of applications, operating systems, or tools. Information types defined in Nomenclature are consolidated into the specification update and are no longer published in other documents.
Nomenclature Errata are design defects or errors. These may cause the processor behavior to deviate from published specifications. Hardware and software designed to be used with any given stepping must assume that all errata documented for that stepping are present on all devices. S-Spec Number is a five-digit code used to identify products. Products are differentiated by their unique characteristics such as, core speed, L2 cache size, package type, etc.
Summary Tables of Changes The following tables indicate the errata, specification changes, specification clarifications, or documentation changes which apply to the processor. Intel may fix some of the errata in a future stepping of the component, and account for the other outstanding issues through documentation or specification changes as noted. These tables uses the following notations: Codes Used in Summary Tables Stepping X: Errata exists in the stepping indicated.
Errata (Sheet 2 of 5) Steppings Number Status ERRATA E-1 L-1 BU7 X X No Fix General Protection Fault (#GP) for Instructions Greater than 15 Bytes May be Preempted BU8 X X No Fix LBR, BTS, BTM May Report a Wrong Address when an Exception/Interrupt Occurs in 64-bit Mode BU9 X X No Fix Incorrect Address Computed For Last Byte of FXSAVE/FXRSTOR or XSAVE/XRSTOR Image Leads to Partial Memory Update BU10 X X No Fix Values for LBR/BTS/BTM Will be Incorrect after an Exit from SMM BU11 X X
Errata (Sheet 3 of 5) Steppings Number Status ERRATA E-1 L-1 BU34 X X No Fix Processor May Fail to Acknowledge a TLP Request BU35 X X No Fix An Unexpected PMI May Occur After Writing a Large Value to IA32_FIXED_CTR2 BU36 X X No Fix A Write to the IA32_FIXED_CTR1 MSR May Result in Incorrect Value in Certain Conditions BU37 X X No Fix PCIe* LTR Incorrectly Reported as Being Supported BU38 X X No Fix PerfMon Overflow Status Can Not be Cleared After Certain Conditions Have Occurred
Errata (Sheet 4 of 5) Steppings Number Status ERRATA E-1 L-1 BU63 X X No Fix PCIe* Root-port Initiated Compliance State Transmitter Equalization Settings May be Incorrect BU64 X X No Fix PCIe* Controller May Incorrectly Log Errors on Transition to RxL0s BU65 X X No Fix Reception of Certain Malformed Transactions May Cause PCIe* Port to Hang Rather Than Reporting an Error BU66 X X No Fix PCIe* Link Width May Degrade After a Warm Reset BU67 X X No Fix MSR_PKG_Cx_RESIDENCY MSRs May
Errata (Sheet 5 of 5) Steppings Number Status ERRATA E-1 L-1 BU94 X X No Fix Instruction Fetches Page-Table Walks May be Made Speculatively to Uncacheable Memory BU95 X X No Fix The Processor May Not Properly Execute Code Modified Using A Floating-Point Store BU96 X X No Fix Execution of GETSEC[SEXIT] May Cause a Debug Exception to be Lost BU97 X X No Fix VM Exits Due to GETSEC May Save an Incorrect Value for “Blocking by STI” in the Context of Probe-Mode Redirection BU98 X X No
§§ Specification Update 13
Identification Information Component Identification using Programming Interface The processor stepping can be identified by the following register contents: Reserved Extended Family1 Extended Model2 Reserved Processor Type3 Family Code4 Model Number5 Stepping ID6 31:28 27:20 19:16 15:14 13:12 11:8 7:4 3:0 00000000b 0011b 00b 0110 1010b xxxxb Notes: 1.
Component Marking Information The processor stepping can be identified by the following component markings. Table 1. Processor Identification (Sheet 1 of 6) Number Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency SR0T2 i7-3920XM E-1 000306A9h 2.9 / 1600 / 650 3/4 core: 3.6 2 core: 3.7 1 core: 3.8 8 2,3,4,5,6 SR0MJ i7-3820QM E-1 000306A9h 2.7 / 1600 / 650 3/4 core: 3.5 2 core: 3.6 1 core: 3.
Table 1. Number SR0MX SR0MY Processor Identification (Sheet 2 of 6) Processor Number i5-3320M i5-3320M Stepping L-1 L-1 Processor Signature 000306A9h 000306A9h Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency Max Intel® Turbo Boost Technology 2.0 Frequency (GHz)1 Shared L3 Cache Size (MB) Notes 2.6 / 1600 / 650 4 core: 0 3 core: 0 2 core: 3.1 1 core: 3.3 3 2,3,4,5,6 2.6 / 1600 / 650 4 core: 0 3 core: 0 2 core: 3.1 1 core: 3.
Table 1. Processor Identification (Sheet 3 of 6) Number Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency SR0X7 i5-3380M L-1 000306A9h 2.9 /1600 /650 2 core: 3.4 1 core: 3.6 3 2,3,4,5,6 SR0X9 i5-3380M L-1 000306A9h 2.9 /1600 /650 2 core: 3.4 1 core: 3.6 3 2,3,4,5,6 SR0XA i5-3340M L-1 000306A9h 2.7 / 1600 /650 2 core: 3.2 1 core: 3.4 3 2,3,4,5,6 SR0XB i5-3340M L-1 000306A9h 2.7 / 1600 /650 2 core: 3.2 1 core: 3.
Table 1. Processor Identification (Sheet 4 of 6) Number Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency SR0ZN i5-3439Y L-1 000306A9h 1.5 /1600/ 350 SR12S i5-3339Y L-1 000306A9h 1.5 /1600/ 350 SR0ZQ i5-3339Y L-1 000306A9h 1.5 /1600/ 350 SR12P i3-3229Y L-1 000306A9h 1.4 /1600/ 350 SR0ZM i3-3229Y L-1 000306A9h 1.4 /1600/ 350 SR12M 2129Y P-0 000306A9h 1.1 / 1600/ 350 SR13W 1019Y P-0 000306A9h 1.
Table 1. Processor Identification (Sheet 5 of 6) Number Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency SR0ND i7-3612QE E-1 00306A9h 2.3 / 1600/ 650 Max Intel® Turbo Boost Technology 2.0 Frequency (GHz)1 Shared L3 Cache Size (MB) Notes 6 2,3,4,5,6,8 4 2,3,4,5,6,8 4 2,3,4,5,6,8 3 2,3,4,5,6,8 3 2,3,4,5,6,8 3 2,4,8 3 2,4,8 3 2,4,8 2 4,8 2 4,8 3/4 Core: 2.8 2 Core: 3.0 1 Core: 3.
Table 1. Number Processor Identification (Sheet 6 of 6) Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency Max Intel® Turbo Boost Technology 2.0 Frequency (GHz)1 Shared L3 Cache Size (MB) Notes 2 4,8 1 4,8 4 Core: 0 SR0VR 1020E P-0 00306A9h 2.2 / 1600/ 650 3 Core: 0 2 Core: 0 1 Core: 0 4 Core: 0 SR10F 927UE P-0 00306A9h 1.5 / 1600/ 350 3 Core: 0 2 Core: 0 1 Core: 0 Notes: 1.
Errata BU1. The Processor May Report a #TS Instead of a #GP Fault Problem: A jump to a busy TSS (Task-State Segment) may cause a #TS (invalid TSS exception) instead of a #GP fault (general protection exception). Implication: Operation systems that access a busy TSS may get invalid TSS fault instead of a #GP fault. Intel has not observed this erratum with any commercially available software. Workaround: None identified. Status: For the steppings affected, see the Summary Tables of Changes. BU2.
BU4. Performance Monitor SSE Retired Instructions May Return Incorrect Values Problem: Performance Monitoring counter SIMD_INST_RETIRED (Event: C7H) is used to track retired SSE instructions. Due to this erratum, the processor may also count other types of instructions resulting in higher than expected values. Implication: Performance Monitoring counter SIMD_INST_RETIRED may report count higher than expected. Workaround: None identified.
BU8. LBR, BTS, BTM May Report a Wrong Address when an Exception/ Interrupt Occurs in 64-bit Mode Problem: An exception/interrupt event should be transparent to the LBR (Last Branch Record), BTS (Branch Trace Store) and BTM (Branch Trace Message) mechanisms.
BU11. EFLAGS Discrepancy on Page Faults and on EPT-Induced VM Exits after a Translation Change Problem: This erratum is regarding the case where paging structures are modified to change a linear address from writable to non-writable without software performing an appropriate TLB invalidation.
BU13. MCi_Status Overflow Bit May Be Incorrectly Set on a Single Instance of a DTLB Error Problem: A single Data Translation Look Aside Buffer (DTLB) error can incorrectly set the Overflow (bit [62]) in the MCi_Status register. A DTLB error is indicated by MCA error code (bits [15:0]) appearing as binary value, 000x 0000 0001 0100, in the MCi_Status register.
BU17. PEBS Record not Updated when in Probe Mode Problem: When a performance monitoring counter is configured for PEBS (Precise Event Based Sampling), overflows of the counter can result in storage of a PEBS record in the PEBS buffer. Due to this erratum, if the overflow occurs during probe mode, it may be ignored and a new PEBS record may not be added to the PEBS buffer. Implication: Due to this erratum, the PEBS buffer may not be updated by overflows that occur during probe mode.
BU21. #GP on Segment Selector Descriptor that Straddles Canonical Boundary May Not Provide Correct Exception Error Code Problem: During a #GP (General Protection Exception), the processor pushes an error code on to the exception handler’s stack. If the segment selector descriptor straddles the canonical boundary, the error code pushed onto the stack may be incorrect. Implication: An incorrect error code may be pushed onto the stack.
BU24. Changing the Memory Type for an In-Use Page Translation May Lead to Memory-Ordering Violations Problem: Under complex microarchitectural conditions, if software changes the memory type for data being actively used and shared by multiple threads without the use of semaphores or barriers, software may see load operations execute out of order. Implication: Memory ordering may be violated. Intel has not observed this erratum with any commercially available software.
BU27. Fault Not Reported When Setting Reserved Bits of Intel® VT-d Queued Invalidation Descriptors Problem: Reserved bits in the Queued Invalidation descriptors of Intel VT-d (Virtualization Technology for Directed I/O) are expected to be zero, meaning that software must program them as zero while the processor checks if they are not zero. Upon detection of a non-zero bit in a reserved field an Intel VT-d fault should be recorded.
BU30. Spurious Interrupts May be Generated From the Intel® VT-d Remap Engine Problem: If software clears the F (Fault) bit 127 of the Fault Recording Register (FRCD_REG at offset 0x208 in Remap Engine BAR) by writing 1b through RW1C command (Read Write 1 to Clear) when the F bit is already clear then a spurious interrupt from Intel VT-d (Virtualization Technology for Directed I/O) Remap Engine may be observed.
BU34. Processor May Fail to Acknowledge a TLP Request Problem: When a PCIe root port’s receiver is in Receiver L0s power state and the port initiates a Recovery event, it will issue Training Sets to the link partner. The link partner will respond by initiating an L0s exit sequence. Prior to transmitting its own Training Sets, the link partner may transmit a TLP (Transaction Layer Packet) request. Due to this erratum, the root port may not acknowledge the TLP request.
BU38. PerfMon Overflow Status Can Not be Cleared After Certain Conditions Have Occurred Problem: Under very specific timing conditions, if software tries to disable a PerfMon counter through MSR IA32_PERF_GLOBAL_CTRL (0x38F) or through the per-counter eventselect (e.g. MSR 0x186) and the counter reached its overflow state very close to that time, then due to this erratum the overflow status indication in MSR IA32_PERF_GLOBAL_STAT (0x38E) may be left set with no way for software to clear it.
BU41. PCI Express* Differential Peak-Peak Tx Voltage Swing May Violate the Specification Problem: Under certain conditions, including extreme voltage and temperature, the peak-peak voltage may be higher than the specification. Implication: Violation of PCI Express® Base Specification of the VTX--DIFF-PP voltage. No failures have been observed due to this erratum. Workaround: None identified. BU42.
BU44. IA32_FEATURE_CONTROL MSR May be Uninitialized on a Cold Reset Problem: IA32_FEATURE_CONTROL MSR (3Ah) may have random values after RESET (including the reserved and Lock bits), and the read-modify-write of the reserved bits and/or the Lock bit being incorrectly set may cause an unexpected GP fault. Implication: Due to this erratum, an unexpected GP fault may occur and BIOS may not complete initialization. Workaround: It is possible for the BIOS to contain a workaround for this erratum.
BU48. 64-bit REP MOVSB/STOSB May Clear The Upper 32-bits of RCX, RDI And RSI Before Any Data is Transferred Problem: If a REP MOVSB/STOSB is executed in 64-bit mode with an address size of 32 bits, and if an interrupt is being recognized at the start of the instruction operation, the upper 32-bits of RCX, RDI and RSI may be cleared, even though no data has yet been copied or written. Implication: Due to this erratum, the upper 32-bits of RCX, RDI and RSI may be prematurely cleared.
BU52. Instructions Retired Event May Over Count Execution of IRET Instructions Problem: Under certain conditions, the performance monitoring event Instructions Retired (Event C0H, Unmask 00H) may over count the execution of IRET instruction. Implication: Due to this erratum, performance monitoring event Instructions Retired may over count. Workaround: None identified. Status: For the steppings affected, see the Summary Tables of Changes. BU53.
BU56. PCI Express* Gen3 Receiver Return Loss May Exceed Specifications Problem: The PCIe Base Specification includes a graph that sets requirements for maximum receiver return loss versus frequency. Due to this erratum, the receiver return loss for common mode and differential mode may exceed those requirements at certain frequencies. Under laboratory conditions, Intel has observed violations of as much as 1 dB.
BU59. PCIe* May Associate Lanes That Are Not Part of Initial Link Training to L0 During Upconfiguration Problem: The processor should not associate any lanes that were not part of the initial link training in subsequent upconfiguration requests from an endpoint. Due to this erratum, the processor may associate any Lane that has exited Electrical Idle, even if it is beyond the width of the initial Link training.
BU63. PCIe* Root-port Initiated Compliance State Transmitter Equalization Settings May be Incorrect Problem: If the processor is directed to enter PCIe Polling.Compliance at 5.0 GT/s or 8.0 GT/s transfer rates, it should use the Link Control 2 Compliance Preset/De-emphasis field (bits [15:12]) to determine the correct de-emphasis level. Due to this erratum, when the processor is directed to enter Polling.Compliance from 2.5 GT/s transfer rate, it retains 2.5 GT/s de-emphasis values.
BU67. MSR_PKG_Cx_RESIDENCY MSRs May Not be Accurate Problem: If the processor is in a package C-state for an extended period of time (greater than 40 seconds) with no wake events, the value in the MSR_PKG_C{2,3,6,7}_RESIDENCY MSRs (60DH and 3F8H–3FAH) will not be accurate. Implication: Utilities that report C-state residency times will report incorrect data in cases of long duration package C-states. Workaround: It is possible for the BIOS to contain a workaround for this erratum.
BU72. PCIe* Root Port May Not Initiate Link Speed Change Problem: The PCIe Base specification requires the upstream component to maintain the PCIe link at the target link speed or the highest speed supported by both components on the link, whichever is lower. PCIe root port will not initiate the link speed change without being triggered by the software when the root port maximum link speed is configured to be 5.0 GT/s. System BIOS will trigger the link speed change under normal boot scenarios.
BU75. VM Exits Due to “NMI-Window Exiting” May Not Occur Following a VM Entry to the Shutdown State Problem: If VM entry is made with the “virtual NMIs” and “NMI-window exiting”, VM-execution controls set to 1, and if there is no virtual-NMI blocking after VM entry, a VM exit with exit reason “NMI window” should occur immediately after VM entry unless the VM entry put the logical processor in the wait-for SIPI state.
BU78. PCIe* Controller May Not Enter Loopback Problem: The PCIe controller is expected to enter loopback if any lane in the link receives two consecutive TS1 ordered sets with the Loopback bit set. Due to this erratum, if two consecutive TS1 ordered sets are received only on certain lanes, the controller may not enter loopback. Implication: Intel has not observed any functional issue with any commercially available PCIe devices.
BU82. PCIe* Link May Fail Link Width Upconfiguration Problem: The processor supports PCIe Hardware Autonomous Width management, in which a PCIe link can autonomously vary its width. Due to this erratum, a link that performs a speed change while in a reduced width may no longer be able to return to a wider link width. Implication: PCIe links that perform speed changes while at a reduced link width may be limited to the link width in effect at the time of the speed change.
BU86. REP MOVSB May Incorrectly Update ECX, ESI, and EDI Problem: Under certain conditions, if the execution of a REP MOVSB instruction is interrupted, the values of ECX, ESI and EDI may contain values that represent a later point in the execution of the instruction than the actual interruption point. Implication: Due to this erratum ECX, ESI, and EDI may be incorrectly advanced, resulting in unpredictable system behavior.
BU89. VEX.L is Not Ignored with VCVT*2SI Instructions Problem: The VEX.L bit should be ignored for the VCVTSS2SI, VCVTSD2SI, VCVTTSS2SI, and VCVTTSD2SI instructions, however due to this erratum the VEX.L bit is not ignored and will cause a #UD. Implication: Unexpected #UDs will be seen when the VEX.L bit is set to 1 with VCVTSS2SI, VCVTSD2SI, VCVTTSS2SI, and VCVTTSD2SI instructions. Workaround: Software should ensure that the VEX.L bit is set to 0 for all scalar instructions.
BU93. During Package Power States Repeated PCIe* and/or DMI L1 Transitions May Cause a System Hang Problem: Under a complex set of internal conditions and operating temperature, when the processor is in a deep power state (package C3, C6 or C7) and the PCIe and/or DMI links are toggling in and out of L1 state, the system may hang. Implication: Due to this erratum, the system may hang. Workaround: It is possible for the BIOS to contain a workaround for this erratum.
BU97. VM Exits Due to GETSEC May Save an Incorrect Value for “Blocking by STI” in the Context of Probe-Mode Redirection Problem: The GETSEC instruction causes a VM exit when executed in VMX non-root operation. Such a VM exit should set bit 0 in the Interruptability-state field in the virtual-machine control structure (VMCS) if the STI instruction was blocking interrupts at the time GETSEC commenced execution.
corresponding counter with the same number on the physical core’s other thread rather than the thread experiencing the event. Processors with SMT disabled in BIOS are not affected by this erratum. The list of affected memory at-retirement events is as follows: MEM_UOP_RETIRED.LOADS MEM_UOP_RETIRED.STORES MEM_UOP_RETIRED.LOCK MEM_UOP_RETIRED.SPLIT MEM_UOP_RETIRED.STLB_MISS MEM_LOAD_UOPS_RETIRED.HIT_LFB MEM_LOAD_UOPS_RETIRED.L1_HIT MEM_LOAD_UOPS_RETIRED.L2_HIT MEM_LOAD_UOPS_RETIRED.
BU104. Processor May Livelock During On Demand Clock Modulation Problem: The processor may livelock when (1) a processor thread has enabled on demand clock modulation via bit 4 of the IA32_CLOCK_MODULATION MSR (19AH) and the clock modulation duty cycle is set to 12.
this field. (The processor correctly stores the guest-physical address of the pagingstructure entry into the “guest-physical address” field in the VMCS.) Implication: Software may not be easily able to determine the page offset of the original memory access that caused the EPT violation. Intel has not observed this erratum to impact the operation of any commercially available software.
processor micro-architectural events may cause an incorrect address translation or machine check on either logical processor. Implication: This erratum may result in unexpected faults, an uncorrectable TLB error logged in IA32_MCi_STATUS.MCACOD (bits [15:0]) with a value of 0000_0000_0001_xxxxb (where x stands for 0 or 1), a guest or hyper visor crash, or other unpredictable system behavior. Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Specification Changes The Specification Changes listed in this section apply to the following documents: • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic Architecture • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2A: Instruction Set Reference Manual A-M • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2B: Instruction Set Reference Manual N-Z • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3A: System Prog
Specification Clarifications The Specification Clarifications listed in this section may apply to the following documents: • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic Architecture • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2A: Instruction Set Reference Manual A-M • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2B: Instruction Set Reference Manual N-Z • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volu
Documentation Changes The Documentation Changes listed in this section apply to the following documents: • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic Architecture • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2A: Instruction Set Reference Manual A-M • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2B: Instruction Set Reference Manual N-Z • Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3A: System Prog
DisplayFamily_Displa yModel DisplayFamily_Display Model DisplayFamily_Displa yModel DisplayFamily_Display Model 0F_xx 06_1C 06_1A 06_1E 06_1F 06_25 06_26 06_27 06_2C 06_2E 06_2F 06_35 06_36 §§ 56 Specification Update
