On 6.5.2016 10:59, Chaitra P B wrote: > In-order to handle this 'MPI2_EVENT_ACTIVE_CABLE_EXCEPTION' event, > driver need to follow below steps, > 1. Unmask the 'MPI2_EVENT_ACTIVE_CABLE_EXCEPTION' event, > so that FW can notify this event to host driver. > 2. After receiving this event, add this event to AEN event queue, > for notifying this event to applications. > 3. Then Print below message in kernel logs if the event data's reason > code is zero, > "Currently an active cable with ReceptacleID <ID_Value> cannot be powered > and devices connected to this active cable will not be seen. This active > cable requires <PowerValue_in_mW> of power" > > This event is only for Intruder/Cutlass HBAs. > > Signed-off-by: Chaitra P B <chaitra.basappa@xxxxxxxxxxxx> Reviewed-by: Tomas Henzl <thenzl@xxxxxxxxxx> Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
