Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1001700.1
Update Date:2009-01-11
Keywords:

Solution Type  Technical Instruction Sure

Solution  1001700.1 :   Emulex HBA on same bus as PGX32[TM] may cause system panics  


Related Items
  • Sun Blade 2000 Workstation
  •  
  • Sun Fire 280R Server
  •  
  • Sun Fire 3800 Server
  •  
  • Sun Fire 6800 Server
  •  
  • Sun Netra 20 Server
  •  
  • Sun Fire V880 Server
  •  
  • Sun Fire 4800 Server
  •  
  • Sun Blade 1000 Workstation
  •  
  • Sun Fire 4810 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Desktops>Workstations
  •  
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  
  • GCS>Sun Microsystems>Servers>NEBS-Certified Servers
  •  

PreviouslyPublishedAs
202312


Description
Emulex HBA on same bus as PGX32[TM] may cause system panics.

Steps to Follow
If the Emulex FC HBA card is placed on the same PCI (Peripheral Component Interconnect) Bus with any other PCI card this will cause the Schizo chip to attempt a 64-bit PIO, a system panic would most likely result. The problem will not occur if the Emulex HBA card is installed alone on a PCI Bus.


UltraSparc [TM] III platforms utilizing the Schizo 2.1 or 2.2 ASIC may experience panics due to address parity errors on the PCI Bus. The problem has been seen on systems using the Emulex FC HBA card in combination with a PGX32 card installed on the same PCI Bus. This condition occurs when a card on the PCI Bus detects a 64-bit parity address error on the PCI Bus while another card on the same PCI Bus is performing a 64-bit PIO.

This problem has only been reported in one specific configuration, an Emulex FC HBA card + PGX32 graphics card on the same bus. The Emulex board detects an address parity error, and signals this via SERR. This leads to a system panic.

The following error messages are displayed prior to a system panic:

WARNING: pcisch-0: PCI fault log start:

PCI SERR

PCI error ocurred on device #6

dwordmask=0 bytemask=0

PCI primary error (0):

pcisch-0: PCI secondary error (0):

pcisch-0: PBM AFAR 0.00000000:

pcisch-0: PCI config space error status (4280):

signalled system error.

pcisch-0: PCI fault log end.

panic[cpu1]/thread=2a10000bd40: pcisch-0: PCI bus 2 error(s)!

It has been determined that the parity errors and panics are occurring because the Schizo chip does not drive the upper address bits during the address phase of a 64-bit PIO transaction. The address bits default to all one's, which is incorrect parity. The Emulex card detects this incorrect parity and issues an SERR. A system panic will follows.

It is recommended that if system panics are occurring to move the Emulex card to its own PCI bus.

If using the PGX32 [TM] graphic card, install Patch ID 109154-10 or higher.

If using the PGX64 [TM] graphic card, install Patch ID 108606-18 or higher



Product
Sun Blade 1000 Workstation
Sun Fire V880 Server
Sun Fire 280R Server
Netra 20 Server
Sun Fire 6800 Server
Sun Fire 4810 Server
Sun Fire 4800 Server
Sun Fire 3800 Server
Sun Blade 2000 Workstation

Emulex HBA, PGX32, system panics
Previously Published As
50396
Internal Comments
For internal Sun use only.

For more detail information refer to FAB <Document: 1000175.1>




Change History
Date: 2008-01-08
User Name: 95826
Action: Update Canceled
Comment: *** Restored Published Content *** canceling update to allow migration to IBIS
Version: 0
Date: 2008-01-08
User Name: 95826
Action: Reassign
Comment: reassigning document to release it in order to allow migration to IBIS
Version: 0

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback