Intel® Celeron® Mobile Processor
P4000 and U3000 Series
Specification Update
November 2010
Document Number: 324456-005
Legal Lines and Disclaimers
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. EXCEPT AS
PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER,
AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELA TING T O S ALE AND/OR USE OF INTEL PRODUCTS INCLUDING
LIABILITY OR WARRANTIES RELA TING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY
PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving,
life sustaining, critical control or safety systems, or in nuclear facility applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.” Intel
reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future
changes to them.
Intel processor numbers are not a measure of performance. Proce ssor numbers differentiate features within each processor family,
not across different processor families. See http://www.intel.com/products/processor_number for details.
The processor may contain design defects or errors known as errata which may cause the product to deviate from published
specifications. Current characterized errata are available on request.Contact your local Intel sales office or your distributor to
obtain the latest specifications and before placing your product order.
Intel, Intel Core, Centrino, Celeron, Pentium, Intel Xeon, Intel SpeedStep and the Intel logo are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
-004-001• Added new processor sku P4600October 2010
-005-001
• Updated C-2 Stepping Microcode Update
• Fixed AAZ69
• Added Errata AAZ10S-11S
• Added Errata AAZ96-AAZ99
• Added Revision/V ersion to cl arify if there are ev er multiple releases
within a month
• Added Errata AAZ100-103
• Updated Errata AAZ32 and AAZ76
July 2010
August 2010
November 2010
4
Specification Update
Preface
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.
This document may also contain information that was not previously published.
Affected Documents
Intel® Celeron® Mobile Processor P4000 and U3000 Series
Datasheet
Related Documents
AP-485, Intel
Instruction
®
Intel
Volume 1: Basic Architecture
®
Intel
Volume 2A: Instruction Set Reference Manual A-M
®
Intel
Volume 2B: Instruction Set Reference Manual N-Z
®
Intel
Volume 3A: System Programming Guide
®
Intel
Volume 3B: System Programming Guide
®
Intel
Manual
®
Intel
Documentation Changes (see note 1)
ACPI Specificationswww.acpi.info
®
Processor Identification and the CPUID
64 and IA-32 Architectures Software Developer’s Manual,
64 and IA-32 Architectures Software Developer’s Manual,
64 and IA-32 Architectures Software Developer’s Manual,
64 and IA-32 Architectures Software Developer’s Manual,
64 and IA-32 Architectures Software Developer’s Manual,
64 and IA-32 Intel Architecture Optimization Reference
64 and IA-32 Architectures Software Developer’s Manual
Document Title
Document Title
Document Number/
Location
324471-001
Document Number/
Location
http://www.intel.com/
design/processor/applnots/
241618.htm
http://www.intel.com/
products/processor/manuals/
index.htm
Notes:
1.Documentation changes for Intel® 64 and IA-32 Architecture Software Developer's Manual volumes 1,
2A, 2B, 3A, and 3B, and bug fixes are posted in the Intel® 64 and IA-32 Architecture Software Developer's Manual Documentation Changes.
Specification Update5
Preface
Nomenclature
Errata are design defects or errors. These may cause the Intel® Celeron® P4000 and
U3000 Mobile Processor Series 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,e.g., core speed, L3 cache size, package
type, etc. as described in the processor identification information table. Read all notes
associated with each S-Spec number.
Specification Changes are modifications to the current published specifications.
These changes will be incorporated in any new release of the specification.
Specification Clarifications describe a specification in greater detail or further
highlight a specification’s impact to a complex design situation. These clarifications will
be incorporated in any new release of the specification.
Documentation Changes include typos, errors, or omissions from the current
published specifications. These will be incorporated in any new release of the
specification.
Note:Errata remain in the specification update throughout the product’s lifecycle, or until a
particular stepping is no longer commercially-available. Under these circumstances,
errata removed from the specification update are archived and available upon request.
Specification changes, specification clarifications and documentation changes are
removed from the specification update when the appropriate changes are made to the
appropriate product specification or user documentation (datasheets, manuals, etc.).
§ §
6
Specification Update
Summary Tables of Changes
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. Specification Change or
Clarification that applies to this stepping.
(No mark)
or (Blank box):This erratum is fixed in listed stepping or specification change
does not apply to listed stepping.
Page
Status
Row
(Page):Page location of item in this document.
Doc:Document change or update will be implemented.
Plan Fix:This erratum may be fixed in a future stepping of the product.
Fixed:This erratum has been previously fixed.
No Fix:There are no plans to fix this erratum.
Change bar to left of table row indicates this erratum is either new or modified from the
previous version of the document.
Each Specification Update item is prefixed with a capital letter to distinguish the
product. The key below details the letters that are used in Intel’s microprocessor
Specification Updates:
Specification Update7
AAZ
Errata (Sheet 1 of 5)
Summary Tables of Changes
Number
StatusERRATA
C-2K-0
AAZ1XXNo FixThe Processor May Report a #TS Instead of a #GP Fault
REP MOVS/STOS Executing with Fast Strings Enabled and
Steppings
AAZ2XXNo Fix
Crossing Page Boundaries with Inconsistent Memory Types May
Use an Incorrect Data Size or Lead to Memory-Ordering
Violations
Code Segment Limit/Canonical Faults on RSM May Be Serviced
AAZ3XXNo Fix
before Higher Priority Interrupts/Exceptions and May Push the
Wrong Address onto the Stack
AAZ4XXNo Fix
AAZ5XXNo Fix
Performance Monitor SSE Retired Instructions May Return
Incorrect Values
Premature Execution of a Load Operation Prior to Exception
Handler Invocation
#GP on Segment Selector Descriptor That Straddles Canonical
Boundary May Not Provide Correct Exception Error Code
8
Specification Update
Summary Tables of Changes
Errata (Sheet 2 of 5)
Number
AAZ21XXNo Fix
AAZ22XXNo Fix
AAZ23XXNo FixIA32_MPERF Counter Stops Counting during On-Demand TM1
AAZ24XXNo Fix
AAZ25XXNo Fix
AAZ26XXNo Fix
AAZ27XXNo Fix
AAZ28XXNo Fix
AAZ29XXNo Fix
AAZ30XXNo Fix
AAZ31XXNo FixTwo xAPIC Timer Event Interrupts May Unexpectedly Occur
AAZ32XXNo Fix
AAZ33XXNo Fix
AAZ34XXNo FixAPIC Error “Received Illegal Vector” May Be Lost
AAZ35XXNo Fix
AAZ36XXNo Fix
AAZ37XXNo FixIA32_PERF_GLOBAL_CTRL MSR May Be Incorrectly Initialized
AAZ38XXNo Fix
AAZ39XXNo Fix
AAZ40XXNo Fix
AAZ41XXNo Fix
AAZ42XXNo Fix
AAZ43XXNo FixPerformance Monitor Counters May Count Incorrectly
Steppings
StatusERRATA
C-2K-0
Improper Parity Error Signaled in the IQ Following Reset When a
Code Breakpoint Is Set on a #GP Instruction
An Enabled Debug Breakpoint or Single Step T rap May Be Taken
after MOV SS/POP SS Instruction If It Is Followed by an
Instruction That Signals a Floating Point Exception
The Memory Controller tTHROT_OPREF Timings May Be Violated
during Self-Refresh Entry
Synchronous Reset of IA32_APERF/IA32_MPERF Counters on
Overflow Does Not Work
Disabling Thermal Monitor While Processor is Hot, Then Reenabling, May Result in Stuck Core Operating Ratio
Writing the Local Vector Table (LVT) When an Interrupt is
Pending May Cause an Unexpected Interrupt
xAPIC Timer May Decrement Too Quickly Following an
Automatic Reload While in Periodic Mode
Changing the Memory Type for an In-Use Page Translation May
Lead to Memory-Ordering Violations
Infinite Stream of Interrupts May Occur If an ExtINT Delivery
Mode Interrupt is Received While All Cores in C6
EOI Transaction May Not Be Sent If Software Enters Core C6
during an Interrupt Service Routine
FREEZE_WHILE_SMM Does Not Prevent Event from Pending
PEBS during SMM
DR6 May Contain Incorrect Information When the First
Instruction after a MOV SS,r/m or POP SS Is a Store
An Uncorrectable Error Logged in IA32_CR_MC2_STATUS May
Also Result in a System Hang
Performance Monitor Counter INST_RETIRED.STORES May
Count Higher Than Expected
Sleeping Cores May Not Be Woken Up on Logical Cluster Mode
Broadcast IPI Using Destination Field Instead of Shorthand
Faulting Executions of FXRSTOR May Update State
Inconsistently
Performance Monitor Event EPT.EPDPE_MISS May Be Counted
While EPT Is Disable
Memory Aliasing of Code Pages May Cause Unpredictable
System Behavior
Specification Update9
Errata (Sheet 3 of 5)
Summary Tables of Changes
Number
AAZ44XXNo Fix
AAZ45XXNo Fix
AAZ46XXNo Fix
AAZ47XXNo Fix
AAZ48XXNo Fix
AAZ49XXNo Fix
AAZ50XXNo Fix
AAZ51XXNo Fix
AAZ52XXNo Fix
AAZ53XXNo Fix
AAZ54XXNo Fix
AAZ55XXNo Fix
AAZ56XXNo Fix
AAZ57XXNo Fix
AAZ58XXNo Fix
AAZ59XXNo Fix
AAZ60XXNo Fix
AAZ61XXNo Fix
AAZ62XXNo Fix
AAZ63XXNo Fix
AAZ64XXNo Fix
Steppings
StatusERRATA
C-2K-0
Performance Monitor Event Offcore_response_0 (B7H) Does Not
Count NT Stores to Local DRAM Correctly
EFLAGS Discrepancy on Page Faults and on EPT-Induced VM
Exits after a Translation Change
Back-to-Back Uncorrected Machine Check Errors May Overwrite
IA32_MC3_STATUS.MSCOD
Corrected Errors with a Yellow Error Indication May Be
Overwritten by Other Corrected Errors
Performance Monitor Events DCACHE_CACHE_LD and
DCACHE_CACHE_ST May Overcount
Performance Monitor Events INSTR_RETIRED and
MEM_INST_RETIRED May Count Inaccurately
A Page Fault May Not Be Generated When the PS Bit Is Set to
"1" in a PML4E or PDPTE
BIST Results May Be Additionally Reported after a
GETSEC[WAKEUP] or INIT-SIPI Sequence
Pending x87 FPU Exceptions (#MF) May Be Signaled Earlier
Than Expected
VM Exits Due to "NMI-Window Exiting" May Be Delayed by One
Instruction
VM Exits Due to EPT Violations Do Not R ecord Information about
Pre-IRET NMI Blocking.
Multiple Performance Monitor Interrupts are Possible on
Overflow of IA32_FIXED_CTR2
LBRs May Not be Initialized During Power-On Reset of the
Processor
LBR, BTM or BTS Records May Have Incorrect Branch From
Information After an Enhanced Intel SpeedStep® Technology
Transition, T-states, C1E, or Adaptive Thermal Throttling
VMX-Preemption Timer Does Not Count Down at the Rate
Specified
Multiple Performance Monitor Interrupts Are Possible on
Overflow of Fixed Counter 0
VM Exits Due to LIDT/LGDT/SIDT/SGDT Do Not Report Correct
Operand Size
DPRSLPVR Signal May Be Incorrectly Asserted on Transition
between Low Power C-states
Performance Monitoring Events STORE_BLOCKS.NOT_STA and
STORE_BLOCKS.STA May Not Count Events Correctly
Storage of PEBS Record Delayed Following Execution of MOV SS
or STI
Performance Monitoring Event FP_MMX_TRANS_TO_MMX May
Not Count Some Transitions
10
Specification Update
Summary Tables of Changes
Errata (Sheet 4 of 5)
Number
AAZ65XXNo Fix
AAZ66XXNo FixLER MSRs May Be Unreliable
AAZ67XXNo Fix
AAZ68XXNo Fix
AAZ69XXN/A
AAZ70XFixed
AAZ71XXNo Fix
AAZ72XXNo Fix
AAZ73XXNo Fix
AAZ74XXNo Fix
AAZ75XXNo FixPCI Express x16 Root Port Incorrectly NAK's a Nullified TLP
Steppings
StatusERRATA
C-2K-0
INVLPG Following INVEPT or INVVPID May Fail to Flush All
Translations for a Large Page
MCi_Status Overflow Bit May Be Incorrectly Set on a Single
Instance of a DTLB Error
Debug Exception Flags DR6.B0-B3 Flags May Be Incorrect for
Disabled Breakpoints
This erratum is removed as it doesn not apply to the Intel
Celeron P4000 and U3000 Mobile Processor Series
Delivery of Certain Events Immediately Following a VM Exit May
Push a Corrupted RIP onto the Stack
A String Instruction That Re-maps a Page May Encounter an
Unexpected Page Fault
Logical Processor May Use Incorrect VPID after VM Entry That
Returns from SMM
MSR_TURBO_RATIO_LIMIT MSR May R eturn Intel® Turbo Boost
Technology Core Ratio Multipliers for Non-Existent Core
Configurations
PCI Express x16 Port Logs Bad TLP Correctable Error When
Receiving a Duplicate TLP
AAZ76XXNo Fix
AAZ77XFixedInternal Parity Error May Be Incorrectly Signaled during C6 Exit
AAZ78XXNo FixPMIs during Core C6 Transitions May Cause the System to Hang
AAZ79XXNo Fix
AAZ80XXNo Fix
AAZ81XFixedTXT.PUBLIC.KEY is Not Reliable
AAZ82XFixed
AAZ83XFixed
AAZ84XXNo Fix
AAZ85XXNo FixProcessor Hangs on Package C6 State Exit
AAZ86XXNo FixA Synchronous SMI May Be Delayed
PCI Express Graphics Receiver Error Reported When Receiver
with L0s Enabled and Link Retrain Performed
2-MB Page Split Lock Accesses Combined with Complex Internal
Events May Cause Unpredictable System Behavior
Extra APIC Timer Interrupt May Occur during a Write to the
Divide Configuration Register
8259 Virtual Wire B Mode Interrupt May Be Dropped When it
Collides With Interrupt Acknowledge Cycle From the Preceding
Interrupt
CPUID Incorrectly Reports a C-State as Available When this
State is Unsupported
The Combination of a Page-Split Lock Access and Data Accesses
That Are Split across Cacheline Boundaries May Lead to
Processor Livelock
Specification Update11
Errata (Sheet 5 of 5)
Summary Tables of Changes
Number
AAZ87XXNo Fix
AAZ88XXNo FixPCI Express Cards May Not Train to x16 Link Width
AAZ89XXNo Fix
AAZ90XXNo FixIO_SMI Indication in SMRAM State Save Area May Be Lost
AAZ91XXNo Fix
AAZ92XXNo FixCKE May go Low Within tRFC(min) After a PD Exit
AAZ93XXNo Fix
AAZ94XXNo Fix
AAZ95XXNo FixVM Entry Loading an Unusable SS Might Not Set SS.B to 1
AAZ96XXNo Fix
AAZ97XXNo Fix
AAZ98XNo Fix
AAZ99XXNo Fix
Steppings
StatusERRATA
C-2K-0
FP Data Operand Pointer May Be Incorrectly Calculated After an
FP Access Which Wraps a 4-Gbyte Boundary in Code That Uses
32-Bit Address Size in 64-bit ModeFP Data Operand Pointer Ma y
Be Incorrectly Calculated After an FP Access Which Wraps a 4Gbyte Boundary in Code That Uses 32-Bit Address Size in 64-bit
Mode
The APIC Timer Current Count Register May Prematurely Read
0x0 While the Timer Is Still Running
FSW May Be Corrupted If an x87 Store Instruction Causes a
Page Fault in VMX Non-Root Operation
Under Certain Low Temperature Conditions, Some Uncore
Performance Monitoring Events May Report Incorrect Results
VM Entry to 64-Bit Mode May Fail if Bits 48 And 47 of Guest RIP
Are Different
Accesses to a VMCS May Not Operate Correctly If CR0.CD is Set
on Any Logical Processor of a Core
Performance Monitor Events for Hardware Prefetches Which
Miss The L1 Data Cache May be Over Counted
Correctable and Uncorrectable Cache Errors May be Reported
Until the First Core C6 Transition
VM Exit May Incorrectly Clear IA32_PERF_GLOBAL_CTRL
[34:32]
AAZ100XNo Fix
AAZ101XXNo Fix
AAZ102XXNo Fix
AAZ103XNo Fix
12
DTSTemperature Data May Be Incorrect On a Return From the
Package C6Low Power State
USB Devices May Not Function Properly With Integrated
Graphics While Running Targeted Stress Graphics Workloads
With Non-Matching Memory Configurations
VM Entry May Omit Consistency Checks Related to Bit 14 (BS)
of the Pending Debug Exception Field in Guest-State Area of the
VMCS
Intel Turbo Boost Technology Ratio Changes May Cause
Unpredictable System Behavior
Specification Update
Summary Tables of Changes
Specification Changes
NumberSPECIFICATION CHANGES
None for this revision of this specification update.
Specification Clarifications
NumberSPECIFICATION CLARIFICATIONS
None for this revision of this specification update.
Documentation Changes
NumberDOCUMENTATION CHANGES
None for this revision of this specification update.
§ §
Specification Update13
Identification Information
Identification Information
Component Identification via Programming Interface
The Intel® Celeron® P4000 and U3000 Mobile Processor Series stepping can be
identified by the following processor signatures:
Reserved
31:2827:2019:1615:1413:1211:87:43:0
Notes:
1.The Extended Family, bits [27:20] are used in conjunction with the Family Code, spec ified in bits [11:8] , to
2.The Extended Model, bits [19:16] in conjunction with the Model Number, specified in bits [7:4], are used to
3.The Processor Type, specifie d in bits [13:12 ] indicates wh ether the proce ssor is an original OEM pr ocessor,
4.The Family Code corresponds to bits [11:8] of the EDX register after RESET, bits [11:8] of the EAX register
5.The Model Number corresponds to bits [7:4] of the EDX register after RESET, bits [7:4] of the EAX register
6.The Stepping ID in bits [3:0] indicates the revision number of that model. See Table 1 for the processor
Extended
Family
00000000b0010b00b01100101bxxxxb
indicate whether the processor belongs to the Intel386®, Intel486®, Pe ntium®, Pe ntium Pro®, P entium®
4, or Intel® Core™ processor family.
identify the model of the processor within the processor’s family.
an OverDrive
after the CPUID instruction is executed with a 1 in the EAX register, and the generation field of the Device
ID register accessible through Boundary Scan.
after the CPUID instruction is executed with a 1 in the EAX register, and the model field of the Device ID
register accessible through Boundary Scan.
stepping ID number in the CPUID information.
®
Extended
1
processor, or a dual processor (capable of being used in a dual processor system).
Model
2
Reserved
Processor
Type
3
Family
4
Code
Model
Number
5
Stepping
ID
6
When EAX is initialized to a value of ‘1’, the CPUID instruction returns the Extended
Family, Extended Model, Processor Type, Family C ode, Mode l Number and Step ping ID
value in the EAX register. Note that the EDX processor signature value after reset is
equivalent to the processor signature output value in the EAX register.
Cache and TLB descriptor parameters are provided in the EAX, EBX, ECX and EDX
registers after the CPUID instruction is executed with a 2 in the EAX register.
The Intel® Celeron® P4000 and U3000 Mobile Processor Series can be identified by
the following register contents:
Processor
Stepping
C-28086h0044h12h
K-08086h0044h18h
Notes:
1.The Vendor ID corresponds to Bits 15:0 of the V endor ID R egister l ocated at offset 00–01h
in the PCI function 0 configuration space.
2.The Device ID corresponds to Bits 15:0 of the Device ID Register located at Device 0 offset
02–03h in the PCI function 0 configuration space.
3.The Revision Number corresponds to Bits 7:0 of the Revision ID Register located at offset
08h in the PCI function 0 configuration space.
4.Correct Host Device ID requires firmware support.
14
Vendor ID
1
Device ID
2
Revision ID
Specification Update
3
Loading...
+ 31 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.