
This patch fixes a situation in which one or several cluster members
would panic if a Memory Channel cable was removed or faulty.

This patch fixes the following problems with Memory Channel in a
cluster environment:
         - a problem with the Memory Channel power off in
           LAN interconnect cluster which causes a cluster wide panic,
         - a user is now allow to kill a LAN interconnect cluster via 
           Memory Channel,
         - supports Memory Channel usage in a LAN cluster.

This patch fixes when the master failover node goes offline during a failover 
and failing over due to parity errors increasing beyond the limit.

This fix addresses a problem in which a bad Memory Channel cable causes a 
cluster member to panic with a panic string of "rm_eh_init" or 
"rm_eh_init_prail".

This patch contains changes that should make Memory Channel failovers work 
better.   It will also handle bad optical cables.

This patch fixes a problem in which a node booting into a cluster hangs
during Memory Channel initialization.

Fix a kernel memory fault in rm_get_lock_master.

Fixes a regression for single physical rail Memory Channel configurations.

This fix cleans up stale data left on an offline physcial rail by the Memory
Channel driver.

Facilitates kernel debugging.

Superfluous "rm_event, index too big" messages may appear on system console.

In a memory channel cluster, rebooting a node without performing a hardware
reset can crash other members with a RM_AUDIT_ACK_BLOCK panic.

This fixes issues associated with the initialization of the RM driver.

In a memory channel cluster, rebooting a node without performing a hardware
reset can crash other members with a RM_AUDIT_ACK_BLOCK panic.

This patch fixes a problem in the Memory Channel driver.

This fixes a problem in the Memory Channel driver.

In a memory channel cluster, rebooting a node without performing a hardware
reset can crash other members with a RM_AUDIT_ACK_BLOCK panic.


