Microcode patches are provided by CPU vendors to correct CPU errata. These errata generally affect a very small number of users, so unless your system is mission. The latest CPU errata release for second generation Intel Core processors. Observation #2 - Is there any structure in the microcode update after the 96 byte header? Add cpu microcode update #151. General Software Issues. Software Issues. This chapter describes software issues related to the Sun Fire X4. M2 server. The numbers given in the section titles are internal tracking numbers for change requests related to the issues. The correct family number is 1. ESX 4. 0 displays 1. Use of 8- GB DIMMs with systems running these or previous versions of ESX is not supported. If v. Switch. 0 uses the default mapping to vmnic. The devices referred to are beyond the control of VMware ESX. How to Identify Physical PCI Slots in the Solaris OSTo identify physical PCI slots in the Solaris OS, insert a PCI card in each slot one- by- one, and record the corresponding path information. The Solaris IB Update 3 package is required.
Reported problems include. Install of OS hangs. Data corruption resulting in disk errors may result if this patch is not installed. If Solaris detects that the workaround for Erratum 1. Solaris logs and displays the following warning message. WARNING: BIOS microcode patch for AMD Athlon(tm) 6. Opteron(tm) processor erratum 1. BIOS to a version containing this microcode patch is HIGHLY recommended or erroneous system operation may occur. Workaround. The BIOS implements the workaround required for Erratum 1. Error messages report that one or more CPUs failed to start. This is less than the number of cores available in a quad- core X4. M2 system with 6 or 8 CPU modules. Such systems must run Solaris 1. Microcode Patch Erratum 1310Microcode Patch Erratum 1312However SLES9 and RHEL4 enumerate RAID1 as sda, with the normal harddrive in slot. Check for an SIA update to fix this issue. After flashing new system firmware, disable the following options in the system BIOS. Advanced/ACPI Configuration/Advanced IRQ0 Legacy Routing for HPET. Advanced/CPU Configuration/Boot CPU APIC ID Lifting. Boot Error Message on RHEL 4. ![]() Errata may cause the Intel U4 (6. 79. 18. 82). A change in Software 2. APIC error on CPU0: 0. APIC error on CPU0: 0. APIC error on CPU0: 0. If this message appears while booting Red Hat Enterprise Linux 4. U4 on a system with 6 or 8 processors, it does not represent an actual error and can be safely ignored. It should not be ignored on other versions of RHEL or other hardware configurations. If any ethernet PCI- E option cards are installed, ports on these option cards will probably get the first port numbers. That assumption may not be valid after an upgrade to RHEL 5. Using more memory than is supported for these RHEL versions causes memory errors. Supported memory configurations are. RHEL 5. U1: maximum 2. GB. To fix this problem, update the lpfc driver to 8. RHEL 5. U2. The following shell command overwrites these sectors with zeros. Virtual Floppy and DVD Not Detected (6. The Service Processor implements virtual floppy and DVD drives so that they each have their own logical unit number (LUN). This may prevent them from being detected on systems that only configure LUN 0 on each port. Add the following line to /etc/modules. On Red Hat systems. On SUSE systems. mkinitrd - v initrd- kernel. Where kernel is a kernel- level identifier, such as “2. You can identify the currently running kernel with this command. You should also rebuild the RAM disks for any other kernel images in /boot that you might use. System functionality is not affected. Only USB 1. 1 is supported. Enter the BIOS Setup utility by pressing the F2 key while the system is booting up and performing the power- on self- test (POST). On the BIOS Main Menu screen, select the Advanced tab to open the Advanced Menu screen. On the Advanced Menu screen, choose USB Configuration. On the USB Configuration screen, change USB Controller Support to USB1. Press and release the right arrow key until the Exit menu screen is displayed. Follow the instructions on the Exit menu screen to save your changes and exit the Setup utility. This error is caused by the fact that the driver is attempting to close the CD/DVD- ROM drive tray. Because this drive does not have a tray, an error is reported. It is safe to ignore this error. This is caused by a bug in the HID driver. This message can be safely ignored. You can then set up your desired swap partition using the commands below. After SLES9 SP3 has finished installation and the server has booted, login as the root user. Issue the following commands in a terminal window. Where swap is the swap partition space. In the /etc/fstab file, make an entry for swap partition (if it not already present), with option default. It should look like the following. Boot- Up ACPI Error Message for SLES9 SP3: Incorrect Return Object Type (6. During SLES9 SP3 boot up, the following message is displayed. ACPI- 0. 20. 1: *** Error: Return object type is incorrect . The message can be safely ignored. In the example shown above, the drive letter is sdb. When the module discovers that no floppy drives are available, it prints the warning message and exits. To suppress the message, add the following line to /etc/modules. Red Hat Enterprise Linux 3 U5 (6. Ignore Keyboard Reset Failed Message (6. If the USB keyboard is connected to either the front or back USB ports, the system running RHEL 3 U5 (6. They might be caused by OS ACPI table creation errors related to an incompatibility between the BIOS and the OS. This problem does not occur if a USB device is connected to the front panel at boot time or if USB 2. This problem is fixed in SUSE version 2. Linux kernel. These are currently available at the following URL. SUN/sle. 9/common/x. The problem was not observed on systems with 4 quad- core CPU modules. If more than 2. 00. GB of RAM is installed, specify mem=2. Install mptlinux- 3. Edit /etc/modprobe. Regenerate the initrd boot image with the following commands. ELsmp. imgmkinitrd /boot/initrd- 2. ELsmp. img 2. 6. 9- 4. ELsmp 4. These messages indicate a shared memory error. No actual problems have been reported in connection with these messages. As a result, a number of messages that begin “mptscsi: Unknown symbol” and “mptscsi: disagrees about version of symbol” are written to the kernel ring buffer. For devices implementing Advanced Error Reporting, set the “Unsupported Request Error Mask” bit in the “Uncorrectable Error Mask” register. Set the “Non- Fatal” and “Fatal Error Reporting Enable” bits, but not the “Unsupported Request Reporting Enable” bit. This Meter button does not work because it requires the Solaris stdperformeter utility, which is not available for bootable diagnostics. Refreshing with F5 does not help. The log is updated when the disk is re- inserted. This was first observed in DOS version 2. This only occurs in non- RAID configurations. Close the MSM- IR application. Using the Windows Service Manager, restart MRMonitor and MSMFramework. Reopen the MSM- IR application. The new Intel Team suite is not compatible with Windows 2. SP2 and Windows 2. R2 platforms. The Intel Team suite can be installed successfully on Windows 2. Windows 2. 00. 8 SP1. Your server’s on- board network ports are on the PCI- X bus and therefore cannot be used to create an Intel NIC team with Windows Server 2. R2. Your Windows installation uses a generic NIC driver that does not include the teaming feature. Install an optional Intel 8. PCIe network interface card (NIC) supported for Windows Server 2. R2. Install the NIC driver. This driver is either included with your card, available from the card manufacturer’s web site or from Intel. Include the on- board network ports as part of a multi- vendor team initiated from the Intel PCIe network card. This has been seen on Windows 2. R2 SP2, 6. 4- bit. Because the workaround impairs I/O performance, it is not enabled by default. To enable the workaround, set the BIOS option “Chipset/South. Bridge Configuration/Force MMIO write non- Posted” to “Enabled.”. Continuous Reboots with Sun Storage. Tek SAS RAID HBA External (6. System with a Sun Storage. Tek SAS RAID HBA External (SG- XPCIESAS- R- EXT- Z), Windows 2. This is caused by the option card picking up the wrong IRQ number, resulting in PCI errors and a Hyper. Transport sync flood. If this is not practical, follow these steps. Download the latest driver from this web page: http: //downloadcenter. Product. Temporarily remove Sun Storage. Tek SAS RAID HBA External, from slot 2. Power the system down and insert the option card into slot 2. Boot the OS in safe mode. Install the driver you downloaded. Microsoft provides a patch to correct this problem. You can also correct this problem by upgrading to Windows 2. Server SP2. These are currently available from the following URLs. Preinstalled Windows Server 2. R2. The Windows Server 2. R2 operating system might be preinstalled on your system. For more information, see Windows Server 2. R2 Operating System in Introduction. WARNING: BIOS microcode patch for AMD Athlon(tm) 6.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |