Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1018904.1 : Emulex LP9802DC HBA Causes Panic on UltraSPARC(R) IIIi Based Systems
PreviouslyPublishedAs 230748 Symptoms When attempting to access data through an Emulex LP9802DC HBA, in UltraSPARC IIIi based systems, a panic can occur. The signature of the panic is: WARNING: pcisch-3: PCI fault log start: PCI iommu error pcisch3: Error 1 on IOMMU TLB entry 3: Context=0 not Writable not Streamable PCI Page Size=8k Address in page a3520000 Memory: Valid not Cacheable Page Frame=0 pcisch-3: PBM AFSR=0x0.00000000 dwordmask=0 bytemask=0 pcisch-3: PCI primary error (0): pcisch-3: PCI secondary error (0): pcisch-3: PBM AFAR 0.00000000:WARNING: pcisch3: PCI config space CSR=0x2a0 PCI iommu error status (3070013): IOMMU translation stat(1): Invalid Error PCI DMA ADDR 0 pcisch-3: PCI fault log end. panic[cpu1]/thread=2a10001fd40: pcisch-3: PCI bus 1 error(s)! panic[cpu1]/thread=2a10001fd40: sync initiated The above panic occurs upon mounting of a file system through the HBA or upon transferring data through the HBA. The Panic string with core was reproduced on s9u5 (S9 12/03) and s8hw3 (S8 7/03). The Panic string without core was reproduced on s9u3 (S9 4/03) and s28hw1 (S8 12/02). Analysis of failure captured in PCI trace exposed a hardware compatibility issue between the card and the default PCI bridge settings used by the JBus-to-PCI I/O Bridge used in these systems (tomatillo). The frame is active for the last data cycles. Tomatillo has to do the "demand fetch" for the last data chunk from the unmapped page. This results in the IOMMU error. Resolution As a result the LP9802DC is NOT supported on these platforms, but will work on other Sun[TM] systems which do not use the UltraSPARC IIIi processor and JBus architecture e.g. Sun Fire[TM] V880 server. Use any other FC-AL HBA listed in the Sun[TM] System Handbook for a Sun-qualified and supported solution. Product Emulex Sun Fire V440 Server Sun Fire V250 Server Sun Fire V240 Server Sun Fire V210 Server Netra 240 Server Sun Blade 1500 Workstation Sun Blade 2500 Workstation Netra 440 Server Netra 240 Server (AC) Internal Comments Emulex had a proposed workaround of changing reg x42 on their bridge chip from x0020 to x0000. This will change secondary Read Multiple prefetch from "Full Prefetch" to "One cache line Prefetch". With this change the systems did NOT panic but performance was negatively impacted for all PCI cards, not just the Emulex card. As a result, Sun[TM] will not be implementing this change for support of a non-Sun[TM] card. Bug ID: 4994857 ESC# 550927 tomatillo, Emulex, LP9802dc, UltraSPARCIIIi, jbus, panic, pci, v210, v240, v250, v440, netra, 240, 440, blade, 1500, 2500 Previously Published As 77042 Change History Date: 2010-12-31 User name: Dencho Kojucharov Action: Currency check Comments: audited by Entry-Level SPARC Content Lead In this article the Product "Emulex" is too broad. In order to publish this document all applicable versions of Emulex must be entered in the product statement. Ex: Sun StorageTek 2 Gb Fibre Channel PCI-X Enterprise HBA, Emulex, Single Port Sun StorageTek 4 Gb Fibre Channel ATCA HBA, Dual Port Sun StorageTek 4 Gb Fibre Channel ExpressModule HBA, Emulex, Dual Port Sun StorageTek Dual 4 Gb FC Dual GbE ExpressModule HBA, Emulex Emulex LightPulse LP8000 Fibre Channel PCI Host Bus Adapter Sun StorageTek 2 Gb Fibre Channel PCI-X Enterprise HBA, Emulex, Dual Port Sun StorageTek 4 Gb Fibre Channel PCIe HBA, Emulex, Single Port Sun StorageTek 4 Gb Fibre Channel PCIe HBA, Emulex, Dual Port Sun StorageTek Enterprise Class 4 Gb Fibre Channel PCI-X HBA, Emulex, Dual Port Sun StorageTek Enterprise Class 4 Gb Fibre Channel PCI-X HBA, Emulex, Single Port Sun StorageTek Enterprise Class 8 Gb FC PCIe HBA, Emulex, Dual Port Sun StorageTek Enterprise Class 8 Gb FC PCIe HBA, Emulex, Single Port You can look up the possibilities using the Swordfish. Lookup tool (gives proper product Nomenclature). http://krep.emea.sun.com/stats/swordfish/ Search Emulex and after clicking on applicable versions click Result button and copy and paste into product statement. Date: 2005-05-19 User Name: 97961 Action: Approved Comment: Publishing. No further edits required. Date: 2005-05-19 User Name: 97961 Action: Accept Comment: Version: 0 Attachments This solution has no attachment |
||||||||||||
|