Sun Fire E6900 Server
 
Sun Fire 3800 Server
 
Sun Fire 6800 Server
 
Sun Fire E4900 Server
 
Sun Fire 4800 Server
 
Sun Fire V1280 Server
 
Sun Fire E2900 Server
 
Sun Fire 4810 Server
 

GCS>Sun Microsystems>Servers>Midrange V and Netra Servers
 
GCS>Sun Microsystems>Servers>Midrange Servers
 

What action should be taken when an IOMMU TLB(Transaction Look aside Buffer)
error occurs on a Sun Fire[TM] server ?

WARNING: pcisch3 PCI fault log start:
PCI iommu error
pcisch3: Error 1 on IOMMU TLB entry b: Context=0 not Writable not Streamable
PCI Page Size=8k Address in page c6960000
Memory: Valid not Cacheable Page Frame=0
PCI error ocurred on device #1
pcisch3(pci@19,600000): PBM AFSR=0x0.00000000dwordmask=0 bytemask=0
pcisch3(pci@19,600000): PCI primary error (0):
pcisch3(pci@19,600000): PCI secondary error (0):
pcisch3(pci@19,600000): PBM AFAR 0.00000000:
pcisch3: PCI config space CSR=0xaa0
pcisch3(pci@19,600000): PCI fault log end.
Scrubbing PCI iommu TLB entries
No fatal PCI bus error(s)

Above, is an error message from the PCI nexus driver, where device #1 has an
error logged against it, relating to an erroneous entry in the IOMMU TLB.
(Transaction look aside buffer).

The pcisch instance then called the scrubber to clear the error
inside the TLB.

This is a non-fatal error and should, if not occurring very frequently,
lead to no further action, that is, no hardware or software intervention
is needed.

However, if this starts to occur frequently, further investigation
will be required.

See Technical Instruction <Document: 1004769.1> for an in depth discussion on this and other PCI Bus issues and theories.

The Sun Fire v1280 / Netra 1280 and the Sun Fire 2900 can experience this

issue more frequently than other systems. Please make sure that the switch

to which the system is connected, is set to Gigabit speed, and that the system

itself is also running the interfaces at Gigabit speed.

Please see CR 6217062 for more information

This solution has no attachment