Update of IPMI drivers for RHEL 5.1.
Update request for RHEL 5.0 IPMI drivers to be brought up to 2.6.21 or greater
for RHEL 5.1. Patch set consists of changes that have been accepted upstream.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
You can download this test kernel from http://people.redhat.com/dzickus/el5
RHEL 5.1 includes an update of the IPMI driver set to include the upstream
changes as of 220.127.116.11, (with some patches pulled in from 2.6.22-rc4). Specific
changes include the following:
 Fix unitialized data bug in ipmi_si_intf
 Do not start kipmid if driver supports interrupts
 Allow users to override the kernel daemon enable, (force_kipmid)
 Per channel command registration
 Remove interface number limits, (MAX_IPMI_INTERFACES is no longer used)
 Support for hot system interface remove
 Addition of maintenance mode to support firmware updates
 Add poweroff support for the pigeonpoint IPMC
 Fixed BT subdriver to survive long timeouts
 Addition of pci_remove handling for proper cleanup on hot remove
 Misc changes, pci_register_driver conversion, set all return codes to
negative valuse, resolve PROC_FS warnings, addition of a poll delay to
timeout commands, remove static allocations initialized to 0, increase KCS
message size to IPMI_MAX_MSG_SIZE, set the proper addr ype, (IO/MEM), in
the ACPI init code.
New module parameters are discussed, outlined, in Documentation/IPMI.txt.
looking through the notes again, edited:
* hot system interface is no longer supported
* hot system interface removal is now supported
which i assume is correct?
Correct, hot system interface removal is now supported.
Confirmed that the update ipmi driver is in the -47.el5 kernel
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.