E23080

SPARC T4-2 Server

Product Notes

Part No.: E23080-02November 2011

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected byintellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to usin writing.If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, thefollowing notice is applicable:U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are"commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in anyinherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. OracleCorporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks orregistered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks ofAdvanced Micro Devices. UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information on content, products, and services from third parties. OracleCorporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, andservices. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-partycontent, products, or services.

Copyright © 2011, Oracle et/ou ses affiliés. Tous droits réservés.Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à desrestrictions d’utilisation et de divulgation. Sauf disposition de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire,diffuser, modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et parquelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté àdes fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’ellessoient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence dece logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique :U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customersare "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pasconçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vousutilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, desauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliésdéclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type d’applications.Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nom mentionné peut correspondre à des marquesappartenant à d’autres propriétaires qu’Oracle.Intel et Intel Xeon sont des marques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont desmarques ou des marques déposées de SPARC International, Inc. AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marquesdéposées d’Advanced Micro Devices. UNIX est une marque déposée d’The Open Group.Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens donnant accès à des contenus, des produits etdes services émanant de tiers. Oracle Corporation et ses affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ouservices émanant de tiers. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour responsables des pertes subies, des coûtsoccasionnés ou des dommages causés par l’accès à des contenus, produits ou services tiers, ou à leur utilisation.

PleaseRecycle

Contents

Using This Documentation vii

1. Late-Breaking Information 1

Preinstalled Software 1

Supported Oracle Solaris OS, Firmware, and Software 2

Required Patches and Package Updates 2

Oracle Solaris 10 OS Patches 3

Oracle Solaris 11 OS Package Updates 3

2. Known Product Issues 5

Hardware Issues 5

Direct I/O Support 5

Use Links Labeled SPARC T3 to Download sas2ircu Software for SPARC T4Servers 6

Installing Sun Storage 6 Gb SAS PCIe RAID HBA, Internal, Disables the DVDDrive 6

Sun Type 6 Keyboards Are Not Supported by SPARC T4 Series Servers 7

I/O Performance Might Degrade When Using More Than Two Ports AcrossMultiple Sun Dual 10 GbE SFP+ PCIe Cards (CR 6943558) 7

Enable Flow Control (Include System Reboot) 7

Enable Flow Control (Without System Reboot) 7

Sun Storage 6 Gb SAS PCIe RAID HBA, Internal, Must Be Installed In PCIe2Slot 0 (CR 6982358) 8

Server Panics When Booting From a USB Thumbdrive Attached to the FrontUSB Ports (CR 6983185) 8

Cannot Plumb Sun Quad GbE x8 PCIe Low Profile Adapter in PCIe Slot 0When More Than Five Are Installed (CR 6993897) 9

Front-Panel Video Port Does Not Support Resolutions Greater Than 1024 x 768(CR 7021609) 9

PSH Might Not Clear a Retired Cache Line on a Replaced Motherboard (CR7031216) 9

Restrictions on Placement of HBAs in Slot 4 and Slot 5 (CR 7046966) 10

PCIe Correctable Errors Might Be Reported (CR 7051331) 10

L2 Cache Uncorrectable Errors Might Lead to an Entire Processor BeingFaulted (CR 7065563) 11

L2 Cache UEs Are Sometimes Reported as Core Faults Without Any CacheLine Retirements (CR 7071237) 15

Upon a Reboot After an Unrecoverable Hardware Error, CPUs Might Not Start(CR 7075336) 15

Oracle Solaris OS Issues 15

Custom nvalias Settings Do Not Change During a SystemReconfiguration 16

Cannot Boot Oracle Solaris 10 10/09 OS From the Internal DVD 16

The cfgadm -al Command Takes a Long Time to Print Output (CR6937169) 16

Spurious Interrupt Message in System Console (CR 6963563) 18

Spurious Error Message During Initial Oracle Solaris OS Installation (CR6971896) 18

When diag-switch? Is Set to true, Oracle Solaris OS Fails to UpdateEEPROM for Automatic Rebooting (CR 6982060) 19

Memory Allocation Issues With Emulex 8Gb HBAs in a Magma I/OExpansion Box (CR 6982072) 20

Fault Management Sometimes Sends Resolved Cases to the SP (CR 6983432)21

iv SPARC T4-2 Server Product Notes • November 2011

Gigabit Ethernet (nxge) Driver Not Loading on Systems With Oracle Solaris10 10/09 OS and a Solaris 10 9/10 Patchset or Solaris 10 8/11 Patchset (CR6995458) 22

nxge Driver Warning Messages Appear After Reboot (CR 7037575) 23

The cfgadm Command Fails for Certain HBAs (CR 7044759) 23

Watchdog Timeouts Seen With Heavy Workloads and Maximum MemoryConfigurations (CR 7083001) 24

Benign Error Message: mptsas request inquiry page 0x83 fortarget:a, lun:0 failed! (CR 7092982) 25

Oracle VTS dtlbtest Hangs When the CPU Threading Mode Is Set to max-ipc (CR 7094158) 25

Firmware Issues 25

Timestamp for an Oracle ILOM Fault/Critical Event Might Be Off by OneHour (CR 6943957) 26

e1000gDriver Generates Spurious ereportsWhen Installing Oracle SolarisOS Over a Sun PCIe Dual Gigabit Ethernet Adapter (CR 6958011) 26

Missing Interrupt Causes USB Hub Hot-plug Thread to Hang, Resulting InProcess Hangs (CR 6968801) 27

sas2ircu Message That RAID Volume Sizes Other Than “MAX” Are NotSupported (CR 6983210) 27

Units Used to Define the MIB Power Management Time Limit Are Reportedin Seconds (CR 6993008) 28

Message From cpustat Refers to Processor Documentation Incorrectly (CR7046898) 28

reboot disk Command Occasionally Fails When disk Argument Picks UpExtra Characters (CR 7050975) 28

A Sequence of Errors in a CPU’s Register Might Block Strand Retirement forSome Earlier Errors (CR 7071974) 28

Blue LED On Drive Does Not Light When the Drive Is Ready to Remove (CR7082700) 29

Documentation Issues 29

Hardware RAID Guidelines are Missing from Administration Guide 29

Contents v

vi SPARC T4-2 Server Product Notes • November 2011

Using This Documentation

This document contains late-breaking information and known issues for Oracle’sSPARC T4-2 server.

■ “Related Documentation” on page vii

■ “Feedback” on page viii

■ “Support and Accessibility” on page viii

Related Documentation

FeedbackProvide feedback on this documentation at:

Documentation Links

All Oracle products http://www.oracle.com/documentation

SPARC T4-2 server http://www.oracle.com/pls/topic/lookup?ctx=SPARCT4-2

Oracle Solaris OS andother systems software

http://www.oracle.com/technetwork/indexes/documentation#sys_sw

Oracle Integrated LightsOut Manager (ILOM) 3.0

http://www.oracle.com/pls/topic/lookup?ctx=ilom30

Oracle VTS 7.0 http://www.oracle.com/pls/topic/lookup?ctx=OracleVTS7.0

http://www.oracle.com/goto/docfeedback

Support and Accessibility

Description Links

Access electronic supportthrough My Oracle Support

http://support.oracle.com

For hearing impaired:http://www.oracle.com/accessibility/support.html

Learn about Oracle’scommitment to accessibility

http://www.oracle.com/us/corporate/accessibility/index.html

viii SPARC T4-2 Server Product Notes • November 2011

CHAPTER 1

Late-Breaking Information

These product notes contain important and late-breaking information about Oracle’sSPARC T4-2 server.

■ “Preinstalled Software” on page 1

■ “Supported Oracle Solaris OS, Firmware, and Software” on page 2

■ “Required Patches and Package Updates” on page 2

Preinstalled SoftwareThe preinstalled Oracle Solaris OS is installed on a ZFS file system as described inthe following table.

Software Location Function

Oracle Solaris 10 8/11 Root disk Slice 0 (and on Slice 3in the ABE).

Operating system

Oracle VM Server for SPARC 2.1 /opt/SUNWldm Manages logical domains

Electronic Prognostics 1.2 /opt/ep Provides early warning of the potentialfor specific FRU faults

Supported Oracle Solaris OS, Firmware,and Software

Note – The download of the Solaris 10 8/11 SPARC Bundle is identified by thenumber 13058415 at http://support.oracle.com.

Required Patches and Package Updates

Note – Oracle Solaris 11 OS uses package updates rather than patches.

TABLE 1-1 Supported versions of the Oracle Solaris OS, Firmware, and Software

Software Supported Versions

Host OS (preinstalled orinstalled by customer)

Oracle Solaris 10 8/11. Must install the patches listed in TABLE 1-2*

* Refer to the README file provided with the patches for additional information, including patch installation instructions.

Host OS (installed by customer) • Oracle Solaris 11 OS• Solaris 10 9/10 OS with the Solaris 10 8/11 SPARC Bundle, followed by the

patches listed in TABLE 1-2

• Solaris 10 10/09 OS with the Solaris 10 8/11 SPARC Bundle, followed by thepatches listed in TABLE 1-2

System firmware 8.1.1.c (Includes Oracle Integrated Lights Out Manager 3.0)

Oracle VM Server for SPARC(LDoms)

Electronic Prognostics on theserver host

2 SPARC T4-2 Server Product Notes • November 2011

Oracle Solaris 10 OS PatchesInstall the patches listed in TABLE 1-2 before using the server with the preinstalledsoftware, or if you have installed Oracle Solaris 10 8/11 OS yourself.

In addition to installing the required patches listed in TABLE 1-1, you shoulddownload and install “Recommended OS Patchset Solaris 10 SPARC”. This patchsetcontains Oracle Solaris 10 OS patches that address current Sun Alerts.

If you want to use an earlier version of the Oracle Solaris OS, you must install theSolaris 10 8/11 SPARC Bundle. After installing the Solaris 10 8/11 SPARC Bundle,you must then install the required patches listed in TABLE 1-2.

Oracle Solaris 11 OS Package UpdatesNo package updates are required at this time to use Oracle Solaris 11 OS with thisserver.

You should install an Oracle Solaris 11 Support Repository Update (SRU), if one isavailable. Use the pkg command or the package manager GUI to download anyavailable SRU from:

https://pkg.oracle.com/solaris/support

TABLE 1-2 Required Patchs for Oracle Solaris 10 8/11

147440-04

147149-01

147153-01

147707-01

147159-03

Chapter 1 Late-Breaking Information 3

CHAPTER 2

Known Product Issues

The following issues are known to affect Oracle’s SPARC T4-2 servers at the time ofthis release.

■ “Hardware Issues” on page 5

■ “Oracle Solaris OS Issues” on page 15

■ “Firmware Issues” on page 25

■ “Documentation Issues” on page 29

Hardware IssuesThis section describes issues related to SPARC T4-2 server components.

Direct I/O SupportOnly certain PCIe cards can be used as direct I/O endpoint devices on an I/Odomain. You can still use other cards in your Oracle VM Server for SPARCenvironment, but they cannot be used with the Direct I/O feature. Instead, they canbe used for service domains and for I/O domains that have entire root complexesassigned to them.

For the most up-to-date list of supported PCIe cards, refer to:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=REFERENCE&id=1325454.1

Use Links Labeled SPARC T3 to Downloadsas2ircu Software for SPARC T4 ServersTo download sas2ircu firmware and documentation for SPARC T4-1 and T4-2servers from the current LSI web site, you must use links labeled SPARC T3-1 andT3-2. The software and documentation is the same for both sets of servers.

This is the web site for downloading sas2ircu software from LSI:

http://www,lsi.com/sep/Pages/oracle/index.aspx

This is the web site for downloading sas2ircu documentation from LSI:

http://www.lsi.com/sep/Pages/oracle/sparc_t3_series.aspx

Installing Sun Storage 6 Gb SAS PCIe RAID HBA,Internal, Disables the DVD Drive

After installing a Sun Storage 6 GB SAS PCIe RAID HBA into the server, you will nolonger be able to use the front-panel DVD drive.

Inside the SPARC T4-2 server, up to six drives and the optional DVD drive connectto the same drive backplane. Two internal cables connect the drive backplane to themotherboard assembly.

When installing the Sun Storage 6 GB SAS PCIe RAID HBA, you must use thesesame cables to connect the HBA ports to the drive backplane. (To support RAID 5,both cables must be connected.) The HBA supports and manages only RAIDvolumes, not a DVD drive. You will no longer be able to use the front-panel DVDdrive.

Workaround: To access a DVD drive after installing the Sun Storage 6 GB SAS PCIeRAID HBA:

■ Connect an external USB DVD drive to one of the four USB ports on the server.

■ Use the Oracle ILOM Remote Console to control a networked DVD driveremotely.

The Oracle ILOM Remote Console is a Java application that enables you toredirect and control the keyboard, video, mouse, and storage (KVMS) devices of ahost server remotely. Refer to the Oracle ILOM documentation for instructions onusing the Oracle ILOM Remote Console.

Sun Type 6 Keyboards Are Not Supported bySPARC T4 Series ServersSun Type 6 keyboards cannot be used with SPARC T4 series servers.

I/O Performance Might Degrade When UsingMore Than Two Ports Across Multiple Sun Dual10 GbE SFP+ PCIe Cards (CR 6943558)Excessive packet loss might occur when three or more ports are used across multipleSun Dual 10GbE SFP+ PCIe cards on a SPARC T4-2 server. This is likely tosignificantly degrade transmit and receive performance. When only two ports areused, packet loss is minimal and transmit/receive performance is as expected.

Tip – If performance is unsatisfactory, consider performing the workaround.

Workaround: Use one of the following procedures to enable flow control for theinterfaces. This will greatly reduce packet loss and improve performance.

Enable Flow Control (Include System Reboot)1. Add the following lines in /kernel/drv/ixgbe.conf.

2. Reboot the system to have these changes take effect.

Enable Flow Control (Without System Reboot)1. Add the following lines in /kernel/drv/ixgbe.conf.

fm_capable = 0;flow_control = 3;tx_queue_number = 2;rx_queue_number = 6;intr_throttling = 1000;

fm_capable = 0;flow_control = 3;

Chapter 2 Known Product Issues 7

2. Unplumb all the ixgbe interfaces.

3. Issue the update_drv ixgbe command.

4. Plumb all the ixgbe interfaces again.

Sun Storage 6 Gb SAS PCIe RAID HBA, Internal,Must Be Installed In PCIe2 Slot 0 (CR 6982358)If you install the Sun Storage 6 Gb SAS PCIe RAID HBA, Internal, into the server,you must install the card in PCIe2 slot 0 (the slot closest to the power supplies).Installing this card into any other PCIe2 slot is not supported.

Use the existing server cables to connect the PCIe card to the drive backplane. Bothcables must be connected to the PCIe card:

■ Disconnect the SAS cable from the motherboard port labeled DISK0-3 and connectit to the top HBA port labeled PORT0-3.

■ Disconnect the SAS cable from the motherboard port labeled DISK4-7 and connectit to the top HBA port labeled PORT4-7.

Note – Installing a Sun Storage 6 Gb SAS PCIe RAID HBA, Internal, into the systemwill disable the front-panel SATA DVD drive.

Server Panics When Booting From a USBThumbdrive Attached to the Front USB Ports (CR6983185)When attempting to boot a USB thumbdrive inserted in either front USB port (USB2or USB3), the server might panic.

Workaround: Use the server’s rear USB ports (USB0 or USB1) whenever bootingfrom an external USB device.

tx_queue_number = 2;rx_queue_number = 6;intr_throttling = 1000;

Cannot Plumb Sun Quad GbE x8 PCIe LowProfile Adapter in PCIe Slot 0 When More ThanFive Are Installed (CR 6993897)The Ethernet ports of a Sun Quad GbE x8 PCIe Low Profile adapter installed in PCIeslot 0 cannot be plumbed if there are more than five Sun Quad GbE x8 PCIe LowProfile adapters installed in the server. However, up to nine Sun Quad GbE x8 PCIeLow Profile adapters are supported in the server when one of these adapters is notinstalled in slot 0.

Workaround: Do not install a Sun Quad GbE x8 PCIe Low Profile adapter in PCIeslot 0.

Front-Panel Video Port Does Not SupportResolutions Greater Than 1024 x 768 (CR 7021609)The SPARC T4-2 server contains two video HD15 ports, one in the front of the serverand one in the rear of the server. The front video port does not support screenresolutions greater than 1024 x 768.

If you require screen resolutions greater than 1024 x 768, connect the monitor to theserver’s rear video port. The rear video port supports resolutions up to 1280 x 1024.Refer to the SPARC T4 Series Servers Administration Guide and the fbconfig(1M)man page for instructions on using a local graphics monitor.

PSH Might Not Clear a Retired Cache Line on aReplaced Motherboard (CR 7031216)If you replace the replacement enclosure to repair faulty cache on the motherboard,PSH might not clear the cache on the replacement. The cache line remains disabled.

Workaround: Manually clear the disabled cache line by running the followingcommands:

# fmadm repaired fmri | label# fmadm replaced fmri | label

Restrictions on Placement of HBAs in Slot 4 andSlot 5 (CR 7046966)Follow these rules for placement of the following cards in the server.

You can place the following FCoE 10Gb/s Converged Network Adapters in eitherslot 4 or slot 5, but not in both slots:

■ SG-XPCIEFCOE2-Q-SR

■ SG-PCIEFCOE2-Q-SR

■ SG-XPCIEFCOE2-Q-TA

■ SG-PCIEFCOE2-Q-TA

You can place the following Fibre Channel I/O Adapters in either slot 4 or slot 5, butnot in both slots:

■ SG-XPCIE2FC-QF8-N

■ SG-PCIE2FC-QF8-Z

■ SG-XPCIE2FC-EM8-N

■ SG-PCIE2FC-EM8-Z

Workaround: You can populate both slot 4 and slot 5 with HBA cards if you installthe cards before doing a fresh reinstallation of the Oracle Solaris OS.

PCIe Correctable Errors Might Be Reported (CR7051331)In rare cases, PCI Express Gen2 devices in the server might report I/O errors that areidentified and reported by PSH. For example:

--------------- ------------------------------------ -------------- ---------TIME EVENT-ID MSG-ID SEVERITY--------------- ------------------------------------ -------------- ---------Aug 10 13:03:23 a7d43aeb-61ca-626a-f47b-c05635f2cf5a PCIEX-8000-KP Major

Host : dt214-154Platform : ORCL,SPARC-T3-1B Chassis_id :Product_sn :

Fault class : fault.io.pciex.device-interr-corr 67% fault.io.pciex.bus-linkerr-corr 33%Affects : dev:////pci@400/pci@1/pci@0/pci@c dev:////pci@400/pci@1/pci@0/pci@c/pci@0 faulted but still in service

These errors might be an indication of a faulty or incorrectly seated device. Or theseerrors might be erroneous.

Workaround: Ensure that the device is properly seated and functioning. If the errorscontinue, apply patch 147705-01 or higher.

L2 Cache Uncorrectable Errors Might Lead to anEntire Processor Being Faulted (CR 7065563)An L2 cache uncorrectable error might lead to an entire processor being faultedwhen only specific core strands should be faulted.

Workaround: Schedule a service call with your authorized Oracle service provider toreplace the processor containing the faulty core. Until the processor is replaced, youcan return the strands related to the functioning cores to service using the followingprocedure. This procedure restores as much system functionalty as the active coresprovide.

1. Identify the faulty core:

FRU : "/SYS/MB" (hc://:product-id=ORCL,SPARC-T3-1B:product-sn=1052NND107:server-id=dt214-154:chassis-id=0000000-0000000000:serial=1005LCB-1052D9008K:part=541-424304:revision=50/chassis=0/motherboard=0) 67% "FEM0" (hc://:product-id=ORCL,SPARC-T3-1B:product-sn=1052NND107:server-id=dt214-154:chassis-id=0000000-0000000000/chassis=0/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1/pciexdev=0/pciexfn=0/pciexbus=2/pciexdev=12/pciexfn=0/pciexbus=62/pciexdev=0) 33% faulty

Description : Too many recovered bus errors have been detected, which indicates a problem with the specified bus or with the specified transmitting device. This may degrade into an unrecoverable fault. Refer to http://sun.com/msg/PCIEX-8000-KP for more information.

Response : One or more device instances may be disabled

Impact : Loss of services provided by the device instances associated with this fault

Action : If a plug-in card is involved check for badly-seated cards or bent pins. Otherwise schedule a repair procedure to replace the affected device. Use fmadm faulty to identify the device or contact Sun for support.

# fmdump -eV -c ereport.cpu.generic-sparc.l2tagctl-uc

The following example shows the detector portion of the fmdump output for aSPARC T4-2 server.

Note – Key elements in the example are highlighted for emphasis. They would notbe highlighted in the actual output.

In this example, the faulted chip is indicated by the following FMRI values:

■ Chassis = 0

■ Motherboard = 0

■ Chip = 1

■ Core = 10

These FMRI values correspond to the NAC name:

/SYS/MB/CMP1/CORE2

detector = (embedded nvlist)nvlist version: 0

version = 0x0scheme = hchc-root =hc-list-sz = 4hc-list - (array of embedded nvlists)(start hc-list[0])nvlist version: 0

hc-name = chassishc-id = 0

(end hc-list[0])(start hc-list[1])nvlist version: 0

hc-name = motherboardhc-id = 0

hc-name = chiphc-id = 1

hc-name = corehc-id = 10

(end hc-list[3])

(end detector)

Note – The NAC CORE value is rhe FRMI core value modulo 8.

The following NAC name equivalents are for all CMP cores in a SPARC T4-2server.

2. Save the UUID value provided in the first line of the fmdump output.

You will use this UUID value in the final step of this procedure.

3. Halt the Oracle Solaris OS, and power off the server.

Refer to the Administration Guide for information on powering off the serverwhen the OS is running.

4. At the Oracle ILOM prompt, change directory to the faulty core.

FMRI Values for Cores Corresponding NAC Name

chassis=0 / motherboard=0 / chip=0 /core=0 /SYS/MP/CMP0/CORE0

The following example continues from earlier steps in which the faulty core had aFMRI value of core=10.

5. Disable the faulty core.

6. Power on the server, and restart the Oracle Solaris OS.

Refer to the Administration Guide for information on powering on the serverfrom the Oracle ILOM prompt.

7. Override the FMA diagnosis manually:

The faulty component’s UUID value is provided in the first line of fmdumpoutput.

-> cd /SYS/MB/CMP1/CORE2/SYS/MB/CMP1/CORE2-> show /SYS/MB/CMP1/CORE2 Targets: P0 P1 P2 P3 P4 P5 P6 P7 L2CACHE L1CACHE

Properties: type = CPU Core component_state = Enabled

Commands: cd set show

->set component_state = disabled

# fmadm repair UUID-of-fault

L2 Cache UEs Are Sometimes Reported as CoreFaults Without Any Cache Line Retirements (CR7071237)When a processor cache line encounters an uncorrectable error (UE), the faultmanager is supposed to attempt to retire the cache line involved in the error.Because of this defect, the fault manager might not retire the faulty cache line andinstead reports the entire chip as faulted.

Workaround: Schedule a replacement of the FRU containing the faulty component.For additional information about UEs in processor cache lines, search for message IDSUN4V-8002-WY on the Oracle support site: http://support.oracle.com

Upon a Reboot After an Unrecoverable HardwareError, CPUs Might Not Start (CR 7075336)In rare cases, if the server or sever module experiences a serious problem that resultsin a panic, when the server is rebooted, a number of CPUs might not start, eventhough the CPUs are not faulty.

Example of the type of error displayed:

Workaround: Log in to Oracle ILOM on the SP and power cycle:

Oracle Solaris OS IssuesThis section describes issues related to the Oracle Solaris OS in this release.

rebooting...Resetting...

ERROR: 63 CPUs in MD did not start

-> stop /SYSAre you sure you want to stop /SYS (y/n)? yStopping /SYS-> start /SYSAre you sure you want to start /SYS (y/n) ? yStarting /SYS

Custom nvalias Settings Do Not Change During aSystem Reconfiguration

If you use the nvalias OBP command to make custom system settings, you mustupdate these settings if the system reconfigures itself after a hardware failure.

For example, if the system experiences a hardware failure such as a failed CMP, thesystem will reconfigure the I/O device paths during the next reboot. If you set acustom device path to a boot disk using the nvalias command, the system will notreconfigure the custom device path and the server will not boot the operatingsystem.

Workaround: You must rediscover the device path to the boot disk and update thenvalias setting accordingly.

Cannot Boot Oracle Solaris 10 10/09 OS From theInternal DVDThe internal DVD cannot be used to boot the Oracle Solaris 10 10/09 release.

Note – Later updates of Oracle Solaris 10 do not have this limitation.

Workaround: Remote CD-ROM/DVD (Storage part of rKVMS) can be used to bootthe DVD media itself or the iso image. An external USB DVD drive can also be usedto boot the media.

The cfgadm -al Command Takes a Long Time toPrint Output (CR 6937169)The cfgadm(1M) command for configuring or unconfiguring hot-plug devices takesa long time to complete. For example, the cfgadm -al command could take morethan five minutes before it lists the attachment points for all the hot-plug devices.

Workaround: Use the hotplug(1M) command to manage PCIe hot-plug devices.

Note – The workaround using the hotplug command instead of cfgadm -al onlyworks for PCI devices.

■ Use the hotplug list -l command to list the status of all hot-plug PCIe slots.For example:

■ Use the hotplug disable command to disable a PCIe card.

For example, to disable the EM card in PCI-EM3 and confirm that it is no longerenabled:

You can now physically remove the EM card.

■ Use the hotplug list command to verify that a card is removed.

For example:

■ Use the hotplug poweron command to power on a PCIe card.

For example, to power on the EM card in PCI-EM3 and confirm that it has movedto the POWERED state:

# hotplug list -l | grep PCI-EM/pci@400/pci@1/pci@0/pci@4 [PCI-EM2] (EMPTY)/pci@400/pci@2/pci@0/pci@1 [PCI-EM0] (EMPTY)/pci@400/pci@2/pci@0/pci@2 [PCI-EM1] (EMPTY)/pci@400/pci@2/pci@0/pci@3 [PCI-EM3] (ENABLED)/pci@500/pci@1/pci@0/pci@1 [PCI-EM8] (EMPTY)/pci@500/pci@1/pci@0/pci@2 [PCI-EM10] (ENABLED)/pci@500/pci@2/pci@0/pci@2 [PCI-EM9] (ENABLED)/pci@500/pci@2/pci@0/pci@3 [PCI-EM11] (EMPTY)/pci@600/pci@1/pci@0/pci@4 [PCI-EM4] (EMPTY)/pci@600/pci@1/pci@0/pci@5 [PCI-EM6] (ENABLED)/pci@600/pci@2/pci@0/pci@0 [PCI-EM7] (EMPTY)/pci@600/pci@2/pci@0/pci@5 [PCI-EM5] (EMPTY)/pci@700/pci@1/pci@0/pci@4 [PCI-EM14] (EMPTY)/pci@700/pci@2/pci@0/pci@3 [PCI-EM12] (ENABLED)/pci@700/pci@2/pci@0/pci@4 [PCI-EM13] (EMPTY)/pci@700/pci@2/pci@0/pci@5 [PCI-EM15] (EMPTY)

# hotplug disable /pci@400/pci@2/pci@0/pci@3 PCI-EM3# hotplug list -l | grep PCI-EM3/pci@400/pci@2/pci@0/pci@3 [PCI-EM3] (POWERED)

# hotplug list -l | grep PCI-EM.../pci@400/pci@2/pci@0/pci@3 [PCI-EM3] (EMPTY)...

# hotplug poweron /pci@400/pci@2/pci@0/pci@3 PCI-EM3# hotplug list -l | grep PCI-EM3/pci@400/pci@2/pci@0/pci@3 [PCI-EM3] (POWERED)

■ Use the hotplug enable command to enable a PCIe card.

■ For example, to enable the EM card in PCI-EM3 and confirm that it has moved tothe ENABLED state:

Note – For more information about the hotplug command, see the hotplug(1M)man page.

Spurious Interrupt Message in System Console(CR 6963563)During the normal operation of the server, and when running the Oracle VTS systemexerciser, you might see the following message in the system console:

Workaround: You can safely ignore this message.

Spurious Error Message During Initial OracleSolaris OS Installation (CR 6971896)The miniroot is a bootable root file system that includes the minimum Oracle SolarisOS software required to boot the server and configure the OS. The miniroot runsonly during the installation process.

When the server boots the miniroot for the initial configuration, you might see thefollowing messages in the system console:

# hotplug enable /pci@400/pci@2/pci@0/pci@3 PCI-EM3# hotplug list -l | grep PCI-EM3/pci@400/pci@2/pci@0/pci@3 [PCI-EM3] (ENABLED)

date time hostname px: [ID 781074 kern.warning] WARNING: px0: spuriousinterrupt from ino 0x4date time hostname px: [ID 548919 kern.info] ehci-0#0date time hostname px: [ID 100033 kern.info]

Fatal server error:InitOutput: Error loading module for /dev/fb

giving up.

The messages indicate the Xsun server in the Oracle Solaris OS miniroot cannot finda supported driver for the AST graphics device in the service processor. Thesemessages are legitimate, as the miniroot contains only the Xsun environment, andthe AST framebuffer (astfb) is supported only in the Xorg environment. The Xorgenvironment is included in the installed system, so the graphics device might beused when running the installed Oracle Solaris OS.

When diag-switch? Is Set to true, OracleSolaris OS Fails to Update EEPROM forAutomatic Rebooting (CR 6982060)When installing the Oracle Solaris OS to a device when the OBP diag-switch?parameter is set to true, the Oracle Solaris OS installer fails to update thebootdevice parameter with the new device path where the OS was installed.Therefore, this new device path will not be used during the subsequent automaticsystem reboots.

Under these conditions, the server will display the following error message and youwill not be able to reboot from the device:

On previous systems, the OBP diag-device parameter would set the new devicepath to the boot device when the diag-switch? parameter was set to true. SPARCT4 systems no longer supportdiag-device parameter, so the Oracle Solaris OSinstaller warns that setting the OBP boot-device parameter is not possible.

Workaround: From the Oracle ILOM prompt, set the OBP diag-switch?parameter to false:

/usr/openwin/bin/xinit: Network is unreachable (errno 128):unable to connect to X server/usr/openwin/bin/xinit: No such process (errno 3): Server error.

Installing boot information- Installing boot blocks (cxtxdxsx)- Installing boot blocks (/dev/rdsk/cxtxdxsx)- Updating system firmware for automatic rebooting

WARNING: Could not update system for automatic rebooting

-> set /HOST/bootmode script="setenv diag-switch? false"

Alternatively, you can set this parameter at the OBP ok prompt:

Memory Allocation Issues With Emulex 8GbHBAs in a Magma I/O Expansion Box (CR6982072)Memory allocation errors might occur when four or more 8Gb FC PCI-Express HBA,Emulex cards are used in a Magma I/O expansion box connected to an OracleSPARC T4 series server. The following is an example of the types of messages thatmight be logged in /var/adm/messages with this configuration:

Workaround: Limit the number of 8Gb FC PCI-Express HBA, Emulex cards in aMagma I/O expansion box to no more than three.

ok setenv diag-switch? false

date time hostname emlxs: [ID 349649 kern.info] [ 8.019A]emlxs22: ERROR: 301: Memoryalloc failed. (BPL Pool buffer[1760]. size=1024)date time hostname emlxs: [ID 349649 kern.info] [ 8.019A]emlxs20: ERROR: 301: Memoryalloc failed. (BPL Pool buffer[2765]. size=1024)date time hostname emlxs: [ID 349649 kern.info] [ 8.019A]emlxs24: ERROR: 301: Memoryalloc failed. (BPL Pool buffer[3437]. size=1024)date time hostname emlxs: [ID 349649 kern.info] [13.0363]emlxs22: ERROR: 201:Adapter initialization failed. (Unable to allocate memory buffers.)date time hostname emlxs: [ID 349649 kern.info] [ 5.064D]emlxs22: ERROR: 201:Adapter initialization failed. (status=c)date time hostname emlxs: [ID 349649 kern.info] [ B.1949]emlxs22: ERROR: 101: Driverattach failed. (Unable to initialize adapter.)date time hostname emlxs: [ID 349649 kern.info] [13.0363]emlxs20: ERROR: 201:Adapter initialization failed. (Unable to allocate memory buffers.)date time hostname emlxs: [ID 349649 kern.info] [ 5.064D]emlxs20: ERROR: 201:Adapter initialization failed. (status=c)date time hostname emlxs: [ID 349649 kern.info] [ B.1949]emlxs24: ERROR: 101: Driverattach failed. (Unable to initialize adapter.)date time hostname emlxs: [ID 349649 kern.info] [13.0363]emlxs24: ERROR: 201:Adapter initialization failed. (Unable to allocate memory buffers.)date time hostname emlxs: [ID 349649 kern.info] [ 5.064D]emlxs24: ERROR: 201:Adapter initialization failed. (status=c)date time hostname emlxs: [ID 349649 kern.info] [ B.1949]emlxs24: ERROR: 101: Driverattach failed. (Unable to initialize adapter.)

Fault Management Sometimes Sends ResolvedCases to the SP (CR 6983432)This defect causes previously diagnosed and repaired PSH faults from the host toreappear in Oracle ILOM when the host reboots. It manifests itself as an incorrectreport of a PSH-diagnosed fault represented through the Oracle ILOM CLI, BUI, andfault LED.

You can identify this defect by checking to see if the same PSH fault was reportedfrom the host as well. If it was reported only by Oracle ILOM and not from the host,it is probably an example of this defect.

Recovery Action: Use the Oracle ILOM diagnostic and repair tools to identify theerror condition and correct it. The following example illustrates how to diagnoseand repair a PSH fault diagnosed by the host. This example is based on the OracleILOM fault management shell. You could instead use the Oracle ILOM CLI or BUI toaccomplish the same results.

1. Display the fault information.

2. Check for faults on the host.

faultmgmtsp> fmadm faulty------------------- ------------------------------------ -------------- -------Time UUID msgid Severity------------------- ------------------------------------ -------------- -------2011-09-16/15:38:19 af875d87-433e-6bf7-cb53-c3d665e8cd09 SUN4V-8002-6E Major

Fault class : fault.cpu.generic-sparc.strand

FRU : /SYS/MB(Part Number: 7015272) (Serial Number: 465769T+1130Y6004M)

Description : A fault has been diagnosed by the Host Operating System.

Response : The service required LED on the chassis and on the affectedFRU may be illuminated.

Impact : No SP impact. Check the Host OS for more information.

Action : The administrator should review the fault on the Host OS.Please refer to the Details section of the Knowledge Articlefor additional information.

# fmadm fault# <-- Host displays no faults

3. Verify that the fault shown by Oracle ILOM was repaired on the host.

4. Flush the previously faulty component from the host resource cache.

5. Repair the fault in Oracle ILOM.

Gigabit Ethernet (nxge) Driver Not Loading onSystems With Oracle Solaris 10 10/09 OS and aSolaris 10 9/10 Patchset or Solaris 10 8/11Patchset (CR 6995458)A problem in the Oracle Solaris 10 10/09 package installation process prevents thenxge alias definition for SPARC T4 series servers from being entered in/etc/driver_aliases. Without this alias being properly defined, the nxge cannotbe attached.

Recovery Action: To correct this problem, perform the following steps.

1. Log in as root.

2. Add the following entry to /etc/driver_aliases:

3. Reboot the system.

4. Configure the network interfaces.

# fmdumpTIME UUID SUNW-MSG-IDSep 16 08:38:19.5582 af875d87-433e-6bf7-cb53-c3d665e8cd09 SUN4V-8002-6ESep 16 08:40:47.8191 af875d87-433e-6bf7-cb53-c3d665e8cd09 FMD-8000-4M RepairedSep 16 08:40:47.8446 af875d87-433e-6bf7-cb53-c3d665e8cd09 FMD-8000-6U Resolved#

# fmadm flush /SYS/MBfmadm: flushed resource history for /SYS/MB#

faultmgmtsp> fmadm repair /SYS/MBfaultmgmtsp> fmadm faultyNo faults foundfaultmgmtsp>

nxge "SUNW,niusl-kt"

nxge Driver Warning Messages Appear AfterReboot (CR 7037575)During reboot, nxge warnings such as the following appear in the/var/adm/messages log:

Workaround: These messages can be ignored.

The cfgadm Command Fails for Certain HBAs(CR 7044759)The cfgadm command fails for some HBA devices (such as SGX-SAS6-EXT-Z, SGX-SAS6-INT-Z, SG-SAS6-REM-Z). For example:

Workaround: Disable the fault management daemon before running the svcadmunconfigure command.

After completing the cfadm task, re-enable the fault management daemon:

Apr 18 08:35:56 san-t4-4-0-a nxge: [ID 752849 kern.warning] WARNING: nxge3 : nxge_nlp2020_xcvr_init: Unknown type[0x70756f88] detectedApr 18 08:36:16 san-t4-4-0-a nxge: [ID 752849 kern.warning]WARNING: nxge7 : nxge_nlp2020_xcvr_init: Unknown type [0x70756f88]detected

# cfgadm -c unconfigure Slot1cfgadm: Component system is busy, try again: unconfigure failedWARNING: (pcieb2): failed to detach driver for the device(mpt_sas9) in the Connection Slot1WARNING: (pcieb2): failed to detach driver for the device(mpt_sas9) in the Connection Slot1

# svcadm disable fmd# ps -ef |grep fmd...# cfgadm -c unconfigure PCI-EM0

# svcadm enable fmd

Watchdog Timeouts Seen With Heavy Workloadsand Maximum Memory Configurations (CR7083001)With certain unusual heavy workloads, especially where a highly processor-intensive workload is bound to cpu 0, the host might appear to suddenly reset backto OBP without any sign of there having been a crash or a panic, and the OracleILOM event log will contain a "Host watchdog expired" entry. The problem is moreprevalent on select systems with full memory configurations.

If you see this sort of sudden reset, display the SP event log using this commandfrom the Oracle ILOM CLI:

If you are encountering this error, you’ll see an entry labeled "Host watchdogexpired".

Workaround: If you encounter this error, contact your authorized service provider tosee if a fix is available.

You can also work around this problem by extending the watchdog period byadding this entry to the Oracle Solaris /etc/system file:

This extends the watchdog timeout period to 1 minute (60000 milliseconds).

In extreme cases, you can also disable the watchdog timeout altogether by addingthis entry to the /etc/system file:

A reboot is required for any /etc/system modification to take effect.

If you do not want to reboot the system immediately after editing /etc/system,you can apply a temporary workaround that will take effect immediately. As root,type:

This command creates a temporary processor set containing only cpu 0, preventingapplication workloads from using this processor and preventing this issue fromoccurring.

-> show /SP/logs/event/list

set watchdog_timeout = 60000

set watchdog_enabled = 0

# psrset -c -F 0

Note – If any threads had been bound to cpu 0, they will be unbound.

This temporary processor set will be removed on the next operating system reboot,at which point the /etc/system workaround described above will take effect.

Benign Error Message: mptsas requestinquiry page 0x83 for target:a, lun:0failed! (CR 7092982)You might see the following error message in /var/adm/messages when thesystem boots:

Oracle VTS dtlbtest Hangs When the CPUThreading Mode Is Set to max-ipc (CR 7094158)The Oracle VTS component stress dtlbtest hangs when max-ipc threading modeis set. This issue is not specific to any processor type, and can happen when both thefollowing cases are true:

■ Only one CPU/strand per core is enabled or online.

■ The total number of online CPUs/strands is less than or equal to 128.

Workaround: Do not run the Oracle VTS Processor test in high-stress mode whenOracle VM for SPARC is set to max-ipc mode.

Firmware IssuesThis section describes issues related to the system firmware.

mptsas request inquiry page 0x83 for target:a, lun:0 failed!

Timestamp for an Oracle ILOM Fault/CriticalEvent Might Be Off by One Hour (CR 6943957)The timestamp reported in an email generated in an Oracle ILOM Fault/criticalevent might be one hour later than the timestamp recorded in the event log.

Recovery Action: Check the timestamp recorded in the event log. If it does notmatch the timestamp reported in the email, use the event log time.

e1000g Driver Generates Spurious ereportsWhen Installing Oracle Solaris OS Over a SunPCIe Dual Gigabit Ethernet Adapter (CR 6958011)When installing the Oracle Solaris OS on domains controlled through Sun PCIe DualGigabit Ethernet (UTP or MMF) adapters, the e1000g Gigabit Ethernet driver mightgenerate false error reports on the static direct I/O (SDIO) and primary domains.The following is an example of these spurious reports:

Workaround: You can safely ignore these ereports.

date time ereport.io.pciex.tl.ca nvlist version: 0ena = 0x298a9f62243802

ena = 0x298a9f62243802detector = (embedded nvlist)nvlist version: 0scheme = devdevice-path = /pci@400/pci@1(end detector)

class = ereport.io.pciex.tl.cadev-status = 0x2ue-status = 0x8000ue-severity = 0x62030adv-ctl = 0xfsource-id = 0x600source-valid = 1__ttl = 0x1__tod = 0x4c058b2e 0x1e8813a0

Missing Interrupt Causes USB Hub Hot-plugThread to Hang, Resulting In Process Hangs (CR6968801)When running Oracle VTS on SPARC T4 series platforms, it is possible (althoughrare) for an Oracle VTS test to hang. If this happens, it might cause other processesand commands to hang, including fmadm and prtconf. The hung processes cannotbe killed.

Workaround: Reboot the system. If the problem repeats, contact your authorizedservice provider. Avoid running Oracle VTS in production environments.

sas2ircu Message That RAID Volume SizesOther Than “MAX” Are Not Supported (CR6983210)If you attempt to create a RAID volume smaller than ”MAX”, the following series ofmessages is returned:

It is true that RAID volumes smaller than “MAX” are not supported. However, ifyou want to create a volume below “MAX” size for nonproduction use, the softwarewill allow you to do so. This is not clear from the message.

Workaround: Ignore the messages and answer yes for the question “Do you wantto continue with volume creation (YES/NO)?”.

You are about to create an IR volume.

WARNING: Proceeding with this operation may cause data loss or datacorruption. Are you sure you want to proceed (YES/NO)? yes

WARNING: Volume created with size other than ’MAX’ is not supported.Do you want to continue with volume creation (YES/NO)? n

SAS2IRCU: you must answer "YES" or "yes" to proceed; operation aborted!SAS2IRCU: Error executing command CREATE.

Units Used to Define the MIB Power ManagementTime Limit Are Reported in Seconds (CR 6993008)The MIB should report the sunHwCtrlPowerMgmtBudgetTimelimit inmilliseconds, but the value displayed is in seconds.

Workaround: Understand that the value reported forsunHwCtrlPowerMgmtBudgetTimelimit is in seconds.

Message From cpustat Refers to ProcessorDocumentation Incorrectly (CR 7046898)A message displayed by the cpustat command says:

This document and web site listed in this message are not available.

reboot disk Command Occasionally FailsWhen disk Argument Picks Up Extra Characters(CR 7050975)When running the reboot disk command, extraneous characters are occasionallyadded to the disk argument before it reaches the OpenBoot PROM (OBP). Thisresults in a failure to boot.

Recovery Action: Repeat the boot request.

A Sequence of Errors in a CPU’s Register MightBlock Strand Retirement for Some Earlier Errors(CR 7071974)In some cases, when errors are detected in multiple strands that are using the sameCPU register, a race condition can occur in which the fault manager’s attempt toretire a strand is rejected because the strand is marked as busy.

See the “SPARC T4 User’s Manual” for descriptions of these events.Documentation for Sun processors can be found at:http://www.sun.com/processors/manuals

Blue LED On Drive Does Not Light When theDrive Is Ready to Remove (CR 7082700)When you attempt to unconfigure a drive for removal, the drive’s blue LED thatindicates the drive is ready for removal might not light. This happens after you placea drive in a slot in place of a drive that had a different WWID.

Workaround: If you inserted a drive after booting the server, realize that the blueLED will not perform this function until the server has booted again.

Documentation IssuesThis section describes issues related to product documentation.

Hardware RAID Guidelines are Missing fromAdministration GuideThe following points are important to understand when configuring RAID volumeson a SPARC T4-2 server:

■ Before configuring and using RAID disk volumes on a SPARC T4-2 server, ensurethat you have installed the latest patches for your operating system from here:

https://pkg.oracle.com/solaris/support

■ Volume migration (relocating all RAID volume disk members from one T4-2server to another) is not supported. If you must perform this operation, contactyour authorized Oracle service provider.

Caution – Creating RAID volumes using the on-board disk controllers destroys alldata on member disks.

This information is not provided in the current version of the SPARC T4 SeriesServers Administration Guide.

E23080

Documents

Transcript of E23080

Basic Buffer Overflows Explained

Venture Capital

How Computer Monitors Work

One Flew Over the Cuckoo's Nest

Life Is Just A Dream - Or Is It?

Jan Van Eyck and the Man In A Red Turban

Bhagavad Gita

Chapter 24

Simple Functions in Haskell

Bodybuilding - The Rock Hard Challenge (Month 1 Training)

Personality Development

Rubik's cube solution

Iron Mills Essay

Chapter-01

Star Wars Trivia!

Improve the Color Quality Of Your Monitor

Aesops Fables

United States Constitution

Fortran

18 Tricks to Teach Your Body