Go to main content
oracle home

# Sun Fire X4470 Server Product Notes

Exit Print View

Search Term
Search Scope:
This Document Entire Library
Updated: September 2018

- Sun Fire X4470 Server Product Notes
- Document Information
- Using This Documentation

- Product Documentation Library
- Feedback

- Sun Fire X4470 Product Notes

- Server Security, Software Releases, and Critical Patch Updates

- IMPORTANT - Install Latest OS Updates, Patches, and Firmware

- Changes to TLSv1.1 Configuration Property as of ILOM 4.0.3.x
- Oracle ILOM File Transfer Using URI Fails if Target Password Contains Special Characters (25917655)
- Diagnosing SAS Data Path Failures on Servers Using MegaRAID Disk Controllers
- Deprecation Notice for Oracle ILOM IPMI 2.0 Management Service
- Resolving Warning Messages for Custom CA and Self-Signed SSL Certificates
- Oracle ILOM License Information
- Supported Operating Systems
- Supported Operating Systems
- Supported Operating Systems in Software Releases
- Available Preinstalled Operating Systems
- Oracle Unbreakable Enterprise Kernel for Linux
- Supported Firmware and Software
- Supported Firmware in Software Releases
- Firmware Updates
- Supported Software
- Downloading an OS or Software Applications
- Supported PCIe Cards
- Quantity and Slot Restrictions
- Minimum Firmware Revisions for PCIe Cards
- Sun Flash Accelerator F20 PCIe Card Requirements
- Card Placement and Cooling
- ESM Replacement Interval
- Internal Sun Storage 6Gb SAS PCIe RAID HBA Requirements
- Sun Storage 10GbE FCoE PCIe Low Profile Dual Port CNA and OS Support
- Oracle x86 Products Accessibility

- Hardware Accessibility
- Oracle ILOM Accessibility
- Oracle Hardware Management Pack Accessibility
- BIOS Accessibility
- Documentation Accessibility

- Known Open Issues
- Hardware Known Issues
- Firmware Known Issues
- BIOS Known Issues
- Oracle ILOM Known Issues
- Oracle Solaris Known Issues
- Oracle Linux, SUSE Linux Enterprise Server (SLES), Red Hat Enterprise Linux (RHEL), and Oracle VM Known Issues
- Windows Known Issues
- Documentation Known Issues
- Broken Links in Sun Server X4470 Documentation Library
- Getting Firmware and Software Updates

- Firmware and Software Updates
- Options for Accessing Firmware and Software Updates
- Software Releases
- Getting Updates From Oracle Hardware Installation Assistant or My Oracle Support
- Download Firmware and Software Updates From My Oracle Support
- Installing Updates Using Other Methods
- Oracle Support

Language:

### BIOS Known Issues

Table 7 BIOS Known Issues
Bug ID | Description
--- | ---
15736079 | Amount of Memory Reported by BIOS and System Is Less Than Actual Memory Installed Issue: In the BIOS splash screen and in the main BIOS Setup Utility menu, the system reports 8 MB less memory than installed to account for the Intel architecture's consumptioln of 8 MB of debug memory. Affected Software: Release 1.0 and later Workaround: There is no workaround.
15640750 | BIOS Does Not Issue Warm Reset to Work Around TSC Skew Issue: There is a slight chance that the processor Timestamp Counters (TSC) within each socket will not be synchronized when the system boots. Newer operating systems that are capable of utilizing the TSC as a fast high-resolution time source require the TSC to be synchronized across all sockets to utilize the TSC as a time source. If the TSCs are not synchronized across sockets, these newer operating systems will detect this condition and will fall back to a slower legacy time source. This can result in less than optimal performance for applications that make heavy use of the `gettimeofday()()` system call. SUSE Linux Enterprise Server (SLES) 11 SP1 is the only supported operating system affected by this issue. The error message below reported by SLES 11 SP1 indicates the operating system has detected that TSCs are not synchronized across sockets: `[ 5.166336] checking TSC synchronization [CPU#0 -> CPU#16]:` `[ 5.198009] Measured 685 cycles TSC warp between CPUs, turning off TSC clock.` `[ 0.016000] Marking TSC unstable due to check_tsc_sync_source failed` `[ 2.920006] checking TSC synchronization [CPU#0 -> CPU#17]:` `[ 2.924000] Measured 738 cycles TSC warp between CPUs, turning off TSC clock.` Affected Operating System and Software: SUSE Linux Enterprise Server (SLES) 11 SP1 Release 1.0 and later Workaround: Reboot the server. The TSCs should be properly synchronized following the reboot.

Previous
Next