Intel E6320 Specification Update - Page 30

Values for LBR/BTS/BTM Will be Incorrect after an Exit from SMM

Get Intel E6320 - Core 2 Duo Dual-Core Processor PDF manuals and user guides
UPC - 735858192576
View all Intel E6320 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

BJ32. Values for LBR/BTS/BTM Will be Incorrect after an Exit from SMM Problem: After a return from SMM (System Management Mode), the CPU will incorrectly update the LBR (Last Branch Record) and the BTS (Branch Trace Store), hence rendering their data invalid. The corresponding data if sent out as a BTM on the system bus will also be incorrect. Note: This issue would only occur when one of the 3 above mentioned debug support facilities are used. Implication: The value of the LBR, BTS, and BTM immediately after an RSM operation should not be used. Workaround: None identified. Status: For the steppings affected, see the Summary Tables of Changes. BJ33. Unsupported PCIe* Upstream Access May Complete with an Incorrect Byte Count Problem: PCIe* Upstream IO and Configuration accesses are not supported. If an IO or Configuration request is received upstream, the integrated PCIe controller will treat it as an unsupported request, the request will be dropped, and a completion will be sent with the UR (Unsupported Request) completion status. This completion, according to the PCIe specification, should indicate a byte count of 4. Due to this erratum, the byte count is set to the same byte count as the offending request. Implication: The processor response to an unsupported PCIe access may not fully comply to the PCIe specification. Workaround: PCIe agents should not issue unsupported accesses. Status: For the steppings affected, see the Summary Tables of Changes. BJ34. Malformed PCIe* Transactions May be Treated as Unsupported Requests Instead of as Critical Errors Problem: PCIe MSG/MSG_D TLPs (Transaction Layer Packets) with incorrect Routing Code as well as the deprecated TCfgRD and TCfgWr types should be treated as malformed transactions leading to a critical error. Due to this erratum, the integrated PCIe controller's root ports may treat such messages as UR (Unsupported Requests). Implication: Legacy malformed PCIe transactions may be treated as UR instead of as critical errors. Workaround: None identified. Status: For the steppings affected, see the Summary Tables of Changes. 30 Specification Update

  • 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
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
30
Specification Update
BJ32.
Values for LBR/BTS/BTM Will be Incorrect after an Exit from SMM
Problem:
After a return from SMM (System Management Mode), the CPU will incorrectly update
the LBR (Last Branch Record) and the BTS (Branch Trace Store), hence rendering their
data invalid. The corresponding data if sent out as a BTM on the system bus will also be
incorrect. Note: This issue would only occur when one of the 3 above mentioned debug
support facilities are used.
Implication:
The value of the LBR, BTS, and BTM immediately after an RSM operation should not be
used.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
BJ33.
Unsupported PCIe* Upstream Access May Complete with an Incorrect
Byte Count
Problem:
PCIe* Upstream IO and Configuration accesses are not supported. If an IO or
Configuration request is received upstream, the integrated PCIe controller will treat it
as an unsupported request, the request will be dropped, and a completion will be sent
with the UR (Unsupported Request) completion status. This completion, according to
the PCIe specification, should indicate a byte count of 4. Due to this erratum, the byte
count is set to the same byte count as the offending request.
Implication:
The processor response to an unsupported PCIe access may not fully comply to the
PCIe specification.
Workaround:
PCIe agents should not issue unsupported accesses.
Status:
For the steppings affected, see the Summary Tables of Changes.
BJ34.
Malformed PCIe* Transactions May be Treated as Unsupported
Requests Instead of as Critical Errors
Problem:
PCIe MSG/MSG_D TLPs (Transaction Layer Packets) with incorrect Routing Code as well
as the deprecated TCfgRD and TCfgWr types should be treated as malformed
transactions leading to a critical error. Due to this erratum, the integrated PCIe
controller's root ports may treat such messages as UR (Unsupported Requests).
Implication:
Legacy malformed PCIe transactions may be treated as UR instead of as critical errors.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.