Scientific Linux 3.0.5 Release Notes
The following topics are covered in this document:
- Changes to the Scientific Linux installation program (Anaconda)
- General information
- Kernel-related information
- Changes to drivers and hardware support
- Changes to packages
The following section includes information specific to the Scientific Linux installation program, Anaconda.
In order to upgrade an already-installed Scientific Linux 3.0.x system to 3.0.5, you must use yum or apt to update those packages that have changed. The use of Anaconda to upgrade to 3.0.4 is not supported.
Use Anaconda only to perform a fresh install of Scientific Linux 3.0.4.
This section contains general information not specific to any other section of this document.
- Scientific Linux 3.0.5 now includes the diskdump
facility, which can serve as an alternative to (or be used in
conjunction with) the Netdump facility.
The diskdump facility for i386 systems currently support the aic7xxx, aic79xx, mpt fusion, dpt_i2o, megaraid2, sym53c8xx, sata_promise and ata_piix devices. On ia64 systems, the aic7xxx, aic79xx, mpt fusion, megaraid2, sym53c8xx, and sata_promise devices are supported. On AMD64 and Intel(R) EM64T systems, the aic7xxx, aic79xx, mpt fusion, megaraid2, sym53c8xx, sata_promise, and ata_piix devices are supported.
The sym53c8xx and sata_promise and ata_piix modules are newly supported in Scientific Linux 3.0.5.
Usage of the diskdump facility requires a dedicated disk device or disk partitions that are large enough to contain all physical system memory. In the event of a system crash, memory will be written to the configured disk location. Upon subsequent reboot, the data will be copied from the disk and formatted into a vmcore file, identical in functionality to that created by the netdump facility, and stored in the unique subdirectory /var/crash/. The vmcore file may be analyzed using the crash(8) utility.
The kernel modules required for the diskdump facility are automatically included in the Scientific Linux 3.0.x kernel. The associated user-space diskdump package is named diskdumputils-1.0.1-4, and like netdump, is installed by default.
The available and appropriate disk location must first be configured and then preformatted for use. After formatting, the diskdump facility may be turned on with chkconfig(8), and then the service must be started. Detailed documentation concerning configuration and user tasks is included with the diskdumputils at the following:
Further information can be found in the diskdumpfmt(8), diskdumpctl(8), and savecore(8) man pages.
Changes to the Scientific Linux Installation Program (Anaconda)
This section contains information related to the Scientific Linux 3.0.5 kernel.
- Scientific Linux 3.0.5 now extends Netdump platform
support from i386 to include AMD64, Intel(R) EM64T, and
Documentation concerning configuration of a netdump client can be found in the following document:
Documentation concerning configuration of a netdump server can be found in the following document:
The vmcore file may be analyzed using the crash(8) utility.
For more information on using Netdump, refer to the netdump(8) and netdump-server(8) man pages.
This update includes bug fixes for a number of drivers. The more significant driver updates are listed below. In some cases, the original driver has been preserved under a different name, and is available as a non-default alternative for organizations that wish to migrate their driver configuration to the latest versions at a later time.
The migration to the latest drivers should be completed before the next Scientific Linux update is applied, because in most cases only one older-revision driver will be preserved for each update.
These release notes also indicate which older-revision drivers have been removed from this kernel update. These drivers have the base driver name with the revision digits appended; for example, megaraid_2002.o. You must remove these drivers from /etc/modules.conf before installing this kernel update.
Keep in mind that the only definitive way to determine what drivers are being used is to review the contents of /etc/modules.conf. Use of the lsmod command is not a substitute for examining this file.
Intel(R) Pro/100 Adapter family (e100 driver)
- This driver is updated to version 3.3.6-k2.
- As part of the update of the e100 driver, the module options for e100 are no longer used. The e100 module options continue to exist in Scientific Linux 3.0.5 for compatibility with previous Scientific Linux 3.0.x releases, but they no longer have any effect on the behavior of the new e100 driver. Users who wish to configure the behavior of the e100 driver should use the ETHTOOL_OPTS setting available in the /etc/sysconfig/network-scripts/ifcfg-eth* files.
Intel(R) PRO/1000 Adapters (e1000 driver)
- This driver has been updated to version 184.108.40.206-k2.
Broadcom Tigon3 (tg3 driver)
- This driver has been updated to version 3.22RH.
Broadcom 4400 (b44 driver)
- This driver has been updated to version 0.95.
3ware 9000 Storage Controller (3w-9xxx driver)
- This driver has been updated to version 2.24.00.011fw.
3ware Storage Controller (3w-xxxx driver)
- This driver has been updated to version 1.02.00.037. The 1.02.00.033 driver is preserved.
QLogic Fibre Channel (qla2xxx driver)
- A module parameter has been added to the qla2200 driver to allow the
Reduced Interrupt Operation (RIO) to be turned off. RIO is a firmware
feature that attempts to increase efficiency by delaying interrupts.
RIO provides benefit when there is a heavy load with several commands
outstanding. However, it can reduce performance in other workloads (it
has been especially evident with tape I/O).
Note that the module parameter does not apply to the qla2100 or qla2300 drivers.
Compaq SA53xx Controllers (cciss driver)
- This driver has been updated to version v2.4.54.RH1.
IBM ServeRAID (ips driver)
- The vary_io feature that was enabled for this driver in Scientific Linux 3.0.3 was found to cause adapter hangs in some situations. This feature has been disabled again in the ips driver. Some applications (primarily those that use raw I/O) may experience reduced performance.
This section contains listings of packages that have been updated or added to Scientific Linux 3.0.x as part of 3.0.5.
The following packages have been updated from Scientific Linux 3.0.4:
The following packages have been added to Scientific Linux 3.0.5:
- No packages have been added.
The following packages have been removed from Scientific Linux 3.0.5:
- No packages have been removed.
( x86 )
Changes to Drivers and Hardware Support
Changes to Packages
Last modified 2006-03-29 10:27 AM