Warning: mysql_fetch_array() expects parameter 1 to be resource, boolean given in /home/newdedyk/domains/bkmanuals.com/public_html/includes/pages/manual_inc.php on line 26
Intel BX80638I53320M manuale d’uso - BKManuals

Intel BX80638I53320M manuale d’uso

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

Vai alla pagina of

Un buon manuale d’uso

Le regole impongono al rivenditore l'obbligo di fornire all'acquirente, insieme alle merci, il manuale d’uso Intel BX80638I53320M. La mancanza del manuale d’uso o le informazioni errate fornite al consumatore sono la base di una denuncia in caso di inosservanza del dispositivo con il contratto. Secondo la legge, l’inclusione del manuale d’uso in una forma diversa da quella cartacea è permessa, che viene spesso utilizzato recentemente, includendo una forma grafica o elettronica Intel BX80638I53320M o video didattici per gli utenti. La condizione è il suo carattere leggibile e comprensibile.

Che cosa è il manuale d’uso?

La parola deriva dal latino "instructio", cioè organizzare. Così, il manuale d’uso Intel BX80638I53320M descrive le fasi del procedimento. Lo scopo del manuale d’uso è istruire, facilitare lo avviamento, l'uso di attrezzature o l’esecuzione di determinate azioni. Il manuale è una raccolta di informazioni sull'oggetto/servizio, un suggerimento.

Purtroppo, pochi utenti prendono il tempo di leggere il manuale d’uso, e un buono manuale non solo permette di conoscere una serie di funzionalità aggiuntive del dispositivo acquistato, ma anche evitare la maggioranza dei guasti.

Quindi cosa dovrebbe contenere il manuale perfetto?

Innanzitutto, il manuale d’uso Intel BX80638I53320M dovrebbe contenere:
- informazioni sui dati tecnici del dispositivo Intel BX80638I53320M
- nome del fabbricante e anno di fabbricazione Intel BX80638I53320M
- istruzioni per l'uso, la regolazione e la manutenzione delle attrezzature Intel BX80638I53320M
- segnaletica di sicurezza e certificati che confermano la conformità con le norme pertinenti

Perché non leggiamo i manuali d’uso?

Generalmente questo è dovuto alla mancanza di tempo e certezza per quanto riguarda la funzionalità specifica delle attrezzature acquistate. Purtroppo, la connessione e l’avvio Intel BX80638I53320M non sono sufficienti. Questo manuale contiene una serie di linee guida per funzionalità specifiche, la sicurezza, metodi di manutenzione (anche i mezzi che dovrebbero essere usati), eventuali difetti Intel BX80638I53320M e modi per risolvere i problemi più comuni durante l'uso. Infine, il manuale contiene le coordinate del servizio Intel in assenza dell'efficacia delle soluzioni proposte. Attualmente, i manuali d’uso sotto forma di animazioni interessanti e video didattici che sono migliori che la brochure suscitano un interesse considerevole. Questo tipo di manuale permette all'utente di visualizzare tutto il video didattico senza saltare le specifiche e complicate descrizioni tecniche Intel BX80638I53320M, come nel caso della versione cartacea.

Perché leggere il manuale d’uso?

Prima di tutto, contiene la risposta sulla struttura, le possibilità del dispositivo Intel BX80638I53320M, l'uso di vari accessori ed una serie di informazioni per sfruttare totalmente tutte le caratteristiche e servizi.

Dopo l'acquisto di successo di attrezzature/dispositivo, prendere un momento per familiarizzare con tutte le parti del manuale d'uso Intel BX80638I53320M. Attualmente, sono preparati con cura e tradotti per essere comprensibili non solo per gli utenti, ma per svolgere la loro funzione di base di informazioni e di aiuto.

Sommario del manuale d’uso

  • Pagina 1

    Reference Number: 32677 0 Mobile 3rd Generation Intel ® Core™ Processor Family Specification Update September 2013 Revision 015[...]

  • Pagina 2

    2 Specification Update INFORMA TION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WI TH INTEL PRODUCTS. NO LICENSE, EXP RESS OR IMPLIED, BY ESTOPPEL OR OTHER WISE, TO ANY INTELLECTUAL PROPERTY RI GHTS IS GRANTED BY THIS DOCUMENT . EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FO R SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHA TSOEVER[...]

  • Pagina 3

    Contents Specification Update 3 Contents Revision History ................ ............ ................. ............. ............ ................. ............ ............ 5 Preface .................. ............. ................ ............. ............. ................ ............. ................ ........ 6 Summary Tables of Change s[...]

  • Pagina 4

    Contents 4 Specification Update[...]

  • Pagina 5

    Specification Update 5 Revision History Revision Description Date 001 • Initial Release. April 2012 002 • Added Errata BU69–BU85 • Updated Proc essor Identi fication T able May 2012 003 • Added L -1 stepping t o Component Identificatio n using Programming • Added L -1 step pin g to errata summary table • Updated Proc essor Identi fica[...]

  • Pagina 6

    6 Specification Update 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 system s, [...]

  • Pagina 7

    Specification Update 7 Nomenclature Errata are design defects or errors. These may cause the processor behavior to deviate from published specifications. Hardware and softw are designed to b e used with any giv en 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[...]

  • Pagina 8

    8 Specification Update 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 fu ture stepping of the component, and account for the other outstanding issues through documentation or specif[...]

  • Pagina 9

    Specification Update 9 BU7 XX N o F i x General Protection Fault (#GP) for Instructions Greater than 15 Bytes May be Preempted BU8 XX N o F i x LBR, BTS, BTM May Report a Wrong Address when an Exception/Interrupt Occurs in 64-bit Mode BU9 XX N o F i x Incorrect Address Computed For Last Byte of FXSA VE/FXRSTOR or XSA VE/XRSTOR Image Leads to Partia[...]

  • Pagina 10

    10 Specification Update BU34 XX N o F i x Processor May Fail to Acknowledge a TL P Request BU35 XX N o F i x An Unexpected PMI May Occur After Writing a Large V alue to IA32_FIXED_CT R2 BU36 XX N o F i x A Write to the IA32_FIXED_CTR1 MSR May Result in Incorrect V alue in Certain Conditions BU37 XX N o F i x PCIe* L TR Incorrectly Reported as Being[...]

  • Pagina 11

    Specification Update 11 BU63 XX N o F i x PCIe* Root-port Initiated Compliance S tat e T r ansmitter Equalization Settings May be Incorrect BU64 XX N o F i x PCIe* Controller May Incorrectly Log Errors on Transition to RxL0s BU65 XX N o F i x Reception of Certain Malformed T ransactions May Cause PCIe* Port to Hang Rather Than Reporting an Error BU[...]

  • Pagina 12

    12 Specification Update BU94 X X No Fix Instruction Fetches Page-T able Walks Ma y be Made S peculatively to Uncacheable Memory BU95 X X No Fix The Processor May Not Properly Execute Cod e Modified Using A Floating-Point S tore BU96 X X No Fix Execution of GETSEC[SEXIT] May Cause a Debug Except ion to be Lost BU97 X X No Fix VM Exits Due to GETSEC [...]

  • Pagina 13

    Specification Update 13 § §[...]

  • Pagina 14

    14 Specification Update Identification Information Component Identification us ing Programmin g Interface The processor stepping can be identified by the following register contents: Notes: 1. The Extended F amily , bits [27:20] are used in conjunction with the F amily Co de, specified in bits [11:8], to indicate whether the processor belongs to th[...]

  • Pagina 15

    Specification Update 15 Component Marking Information The processor stepping can be identified by the following component markings. Table 1. Processor Identif ication (Sheet 1 of 6) Number Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MH z) / Processor Graphics Frequency Max Intel ® Turbo Boost Technology 2.0 Frequency[...]

  • Pagina 16

    16 Specification Update SR0MX i5-3320M L -1 000306 A9h 2.6 / 1600 / 650 4 core: 0 3 core: 0 2 core: 3.1 1 core: 3.3 3 2,3,4,5,6 SR0MY i5-3320M L -1 000306A9h 2.6 / 16 00 / 650 4 core: 0 3 core: 0 2 core: 3.1 1 core: 3.3 3 2,3,4,5,6 SR0MZ i5-3210M L -1 000306 A9h 2.5 / 1600 / 650 4 core: 0 3 core: 0 2 core: 2.9 1 core: 3.1 32 , 4 , 6 SR0N0 i5-3210M [...]

  • Pagina 17

    Specification Update 17 SR0X7 i5-3380M L -1 00 0306A9h 2.9 /1600 /650 2 core: 3.4 1 core: 3.6 3 2,3,4,5,6 SR0X9 i5-3380M L -1 00 0306A9h 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.4 3 2,3,4,5,[...]

  • Pagina 18

    18 Specification Update SR0ZN i5-3439Y L-1 000306A9h 1.5 /1600/ 350 2 core: N/A 1 core: 2.3 3 2,3,4,5,6 SR12S i5-3339Y L-1 000306A9h 1.5 /1600/ 350 2 core: N/A 1 core: 2.2 3 2,4,5,6 SR0ZQ i5-3339Y L-1 000306A9h 1.5 /1600/ 350 2 cor e: N/A 1 core: 2.2 3 2,4,5,6 SR12P i3-3229Y L-1 000306A9h 1.4 /1600/ 350 2 core: N/A 1 core: 1.4 32 , 4 SR0ZM i3-3229Y[...]

  • Pagina 19

    Specification Update 19 SR0ND i7-3612QE E-1 00306A9h 2.3 / 1600/ 650 3/4 Core: 2.8 2 Core: 3.0 1 Core: 3.1 6 2,3,4,5,6,8 SR0T5 i 7-3555LE L-1 00306A9h 2.5 / 1600/ 550 4 Core: 0 3 Core: 0 2 Core: 3.0 1 Core: 3.2 4 2,3,4,5,6,8 SR0T6 i7-3517UE L-1 00306A9h 1.7 / 1600/ 350 4 Core: 0 3 Core: 0 2 Core: 2.6 1 Core: 2.8 4 2,3,4,5,6,8 SR0QJ i5-3610ME L-1 00[...]

  • Pagina 20

    20 Specification Update Notes: 1. This column indic ates max imum I ntel ® T urbo Boost T echnology 2.0 fr equency (GHz) for 4,3, 2 or 1 cores active respectiv ely . 2. Intel ® Hyper- Threading T echnology enabled. 3. Intel ® T rusted Ex ecution T echnology (Intel ® TXT) enabled. 4. Intel ® Virtualization T echnology for IA-32, Intel ® 64 and[...]

  • Pagina 21

    Specification Update 21 Errata BU1. The Processor May Report a #TS Instead of a #GP Fault Problem: A jump to a busy TSS (T ask -State Segment) ma y cause a #TS (inv alid TSS ex ception) instead of a #GP f ault (gener al protection exception). Implication: Operation systems that access a busy T SS may get in valid T SS fault instead of a #GP fault. [...]

  • Pagina 22

    22 Specification Update BU4. Performance Monitor SSE Retired Instructions May Return Incorrect Values Problem: Performance Monitoring counter SIMD_INST_RETIRED (Event: C 7H) is used to tr ack retired SSE instructions. Due to this erratum, the processor may also count other types of instructions resulting in higher than expected values. Implication:[...]

  • Pagina 23

    Specification Update 23 BU8. LBR, BTS, BTM May Repor t a Wrong Address when an Exception/ Interrupt Occurs in 64-bit Mode Problem: An exception/interrupt ev ent should be transparent to the LBR (Last Branch R ecord), B T S (Branch T race Store) and B TM (Branch T r ace Message) mechanisms. However , during a specific boundary condition where the ex[...]

  • Pagina 24

    24 Specification Update BU11. EFLAGS Discrepancy o n Page Faults and on EPT-Induce d VM Exits after a Translation Change Problem: This erratum is regarding the case where pa ging structu res are modifi ed to change a linear address from writable to non-writable without software perfo rming an appropriate TLB inv alidation. When a subseque nt access[...]

  • Pagina 25

    Specification Update 25 BU13. MCi_Status Overflow Bit May Be In correctly Set on a Single Instance of a DTLB Error Problem: A single Data T ranslation Look Aside Buffer (D TLB) error can incorrectly set the Overflow (bit [62]) in the MCi_Status regist er . A D TLB error is indicated by MCA error code (bits [15:0]) appearing as binary value, 000x 00[...]

  • Pagina 26

    26 Specification Update BU17. PEBS Record not Upda ted when in Probe Mode Problem: When a performance monitoring counter is configured for PEBS (Precise Ev e nt Based Sampling), overflows of the counter can result in stor age of a PEBS record in the PEBS buffer . Due to this erra tum, if the ov erfl ow occurs during prob e mode, it ma y be ignored [...]

  • Pagina 27

    Specification Update 27 BU21. #GP on Segment Selector Desc riptor 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 str addle s the canonical boundary , the e[...]

  • Pagina 28

    28 Specification Update BU24. Changing the M emory Type for an In-Use Page Transla t ion Ma y Lead to Memory-Ordering Violations Problem: Under complex microarchitectural conditions, if softw are changes the me mory type for data being actively used and shared by mult iple threads without the use of semaphores or barriers, software may see load ope[...]

  • Pagina 29

    Specification Update 29 BU27. Fault Not Reported When Se tting Reserved Bits of Intel ® VT-d Queued Invalidation Descriptors Problem: Reserv ed bits in the Queued Inv alidation descriptors of Intel VT -d (Virtualization T echnology for Directed I/O) are expected to be z ero, mean ing that software must program them as zero while the processor ch e[...]

  • Pagina 30

    30 Specification Update BU30. Spurious Inte rrupts May be Generated From the Intel ® VT-d Remap Engine Problem: If software clears the F (F ault) bit 127 of the F ault Recording Register (FRCD_REG at offset 0x208 in Remap Engine BAR) by wr iting 1b through RW1C command (R ead Write 1 to Clear) when the F bit is already clear then a spurious interr[...]

  • Pagina 31

    Specification Update 31 BU34. Processor May Fail to Acknowledge a TLP Request Problem: When a PCIe root port’s receiver is in R e ceiver L0s power state and the port initiates a Re covery event, it will issue T raining Sets to the link partner . The link partner will respond by initiating an L0s exit sequence. Prior to transmitting its own T rain[...]

  • Pagina 32

    32 Specification Update BU38. PerfMon Overflow Statu s Ca n Not be Cleared After C ertain Conditions Have Occurred Problem: Under very specific timing conditions, if software tries to disable a P erfMon counter through MSR IA32_PERF_GLOBAL_CTRL (0x38F) or through the per-counter event- select (e.g. MSR 0x186) and the counter reached its overflow st[...]

  • Pagina 33

    Specification Update 33 BU41. PCI Express * Differential Peak-Peak Tx Voltage Swing May Violate the Specification Problem: Under certain conditions, including extrem e 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 fai[...]

  • Pagina 34

    34 Specification Update BU44. IA32_FEATURE_CON TR OL MSR May be Uninitialized on a Cold Reset Problem: IA32_FEA TURE_CONTROL MSR (3Ah) may have random v alues after RESET (including the reserved and Lock bits), and th e read-mod ify -write of the reserved bits and/or the Lock bit being incorrectly set may cause an unexpected GP fault. Implication: [...]

  • Pagina 35

    Specification Update 35 BU48. 64-bit REP MOVSB/STOSB May Clea r 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 oper ation, the upper 32-bits of RCX, RDI and RSI ma y [...]

  • Pagina 36

    36 Specification Update BU52. Instructions Retired Event Ma y Over Count Execution of IRET Instructions Problem: Under certain conditions, the performance monitoring event Instructions Retired (Event C0H, Unmask 00H) may over count the ex ecution of IRET instruction. Implication: Due to this err atum, performance monitoring ev ent Instructions R et[...]

  • Pagina 37

    Specification Update 37 BU56. PCI Express* Gen3 Receiver Re turn Loss May Exce ed Specifications Problem: The PCIe Base Specification includes a graph that sets requirements for maximum receiver return loss v ersus frequency . Due to this err atum, the receiver return loss for common mode and differential mode may ex ceed those requirements at cert[...]

  • Pagina 38

    38 Specification Update BU59. PCIe* May Associate Lanes That Are Not Part of Initial Link Training to L0 During Upconfiguration Problem: The processor should not associate any lane s that were not part o f the initial link training in subsequ ent upconfiguration requests from an endpoint. Due to this erratum, the processor may associate any Lane th[...]

  • Pagina 39

    Specification Update 39 BU63. PCIe* Root-port Initiated Comp liance State Transmitter Equalization Settings May be Incorrect Problem: If the processor is directed to enter PCIe P olling.Compliance at 5.0 GT/s or 8.0 GT/s transfer r ates, it should use the Link Control 2 Compliance Preset/De-emphasis field (bits [15:12]) to determine the correct de-[...]

  • Pagina 40

    40 Specification Update BU67. MSR_PKG_Cx_RESIDENCY MS Rs May Not be Accurate Problem: If the processor is in a package C-state fo r an extended period of time (greater than 40 seconds) with no wak e events, the value in the MSR_PKG_C{2,3,6,7}_RESIDENCY MSRs (60D H and 3F8H–3F AH) will not be accurate. Implication: Utilities that report C-state re[...]

  • Pagina 41

    Specification Update 41 BU72. PCIe* Root Port May No t Initiate Link Speed Change Problem: The PCIe Base specification requires the up stream component to maintain the PCIe link at the target link speed or the highest sp eed supported by both components on the link, whichever is lower . PCIe root port w ill not initiate the link speed change withou[...]

  • Pagina 42

    42 Specification Update BU75. VM Exits Due to “NMI-Window Exit ing” May Not Occur Following a VM Entry to the Shutdown State Problem: If VM entry is made with the “virtual NM Is” 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?[...]

  • Pagina 43

    Specification Update 43 BU78. PCIe* Controller May Not Enter Loopback Problem: The PCIe controller is expected to enter loo pback if any lane in the link receives two consecutive TS1 ordered sets with the Loopba ck bit set. Due to this erratum, if two consecutive TS1 ordered sets are received only on certain lanes, the controller may not enter loop[...]

  • Pagina 44

    44 Specification Update BU82. PCIe* Link May Fail Li nk Width Upconfiguration Problem: The processor supports PCIe Hardware Au tonomous Width management, in which a PCIe link can autonomously vary its width. Du e 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. Impl[...]

  • Pagina 45

    Specification Update 45 BU86. REP MOVSB May Incorrectly Update ECX, ESI, and EDI Problem: Under certain conditions, if the ex ecution of a REP MOVSB instruction is interrupted, the values of ECX, ESI and EDI may contain v alues that represent a later point in the execution of the instruction than the actual interruption point. Implication: Due to t[...]

  • Pagina 46

    46 Specification Update BU89. VEX.L is Not Ignored with VCVT*2SI Instructions Problem: The VEX.L bit should be ignored for the VCVTSS2SI, VCVTSD2SI, VCVTTS S2SI, and VCVT TSD2SI instructions, howev er due to this err atum the VEX.L bi t is not ignored and will cause a #UD. Implication: Unexpected #UDs will be seen when the VEX.L bit is set to 1 wit[...]

  • Pagina 47

    Specification Update 47 BU93. During Package Power States Repeated PC Ie* and/or DMI L1 Transitions May Cause a System Hang Problem: Under a complex set of internal conditio ns and operating temper ature, 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 [...]

  • Pagina 48

    48 Specification Update BU97. VM Exit s Due to GETSEC May Save an Inco rrect V alue for “Blocking by STI” in the Context of Probe-Mode Redirect ion Problem: The GETSEC i nstruction caus es a VM exit wh en ex ecuted in VMX n on-root operation. Such a VM exit should set bit 0 in the Interruptability-state field in the virtual-machine control stru[...]

  • Pagina 49

    Specification Update 49 corresponding counter with the same number on the physical core’ s other thread rather than the thread experiencing the ev ent. Proc essors with SMT disabled in BIOS are not affected by this err atum. The list of affected memory at-retirement ev ents is as follows: MEM_UOP_RETIRED.L OADS MEM_UOP_RETIRED.ST ORES MEM_UOP_RET[...]

  • Pagina 50

    50 Specification Update BU104. Processor May Livelock Duri ng On D emand 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_MODULA TION MSR (19AH) and the clock modulation duty cycle is set to 12.5% (02H in bits 3:0 o f the same MSR), and (2) the other [...]

  • Pagina 51

    Specification Update 51 this field. (The processor correctly stores the guest-ph ysical address of the pagi ng- structure entry into the “gue st-ph ysical address” field in the VMC S.) Implication: Software may not be easily able to determin e the page offset of the original memory access that caused the EPT violation. Intel ha s not observed t[...]

  • Pagina 52

    52 Specification Update processor micro-architectur al eve nts may cause an incorrect ad dress translation or machine check on either logical processor . Implication: This erratum may result in unexpected faul ts, an u ncorrectable TLB error logged in IA32_MCi_ST A TUS.MCACOD (bits [15:0]) with a value of 0000_0000_0001_xxxxb (where x stands for 0 [...]

  • Pagina 53

    Specification Update 53 Specification Changes The Specification Changes listed in this section apply to the following documents: •I n t e l ® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic Architecture •I n t e l ® 64 and IA-32 Arch i tec tu res Softwa re Developer’s Manual, Volume 2A: Instruction Set Reference Ma[...]

  • Pagina 54

    54 Specification Update Specification Clarifications The Specification Clarifications listed in this section may apply to the following documents: •I n t e l ® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic Architecture •I n t e l ® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2A: Instruction Set[...]

  • Pagina 55

    Specification Update 55 Documentation Changes The Documentation Changes listed in this section apply to the following documents: •I n t e l ® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic Architecture •I n t e l ® 64 and IA-32 Arch i tec tu res Softwa re Developer’s Manual, Volume 2A: Instruction Set Reference Ma[...]

  • Pagina 56

    56 Specification Update § § 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[...]