This bug has been copied from bug #636233 and has been proposed
to be backported to 6.0 z-stream (EUS).
Cannot reproduce this issue with "Emulex LPe12002-M8".
It's firmware version is :
1.11A5 (U3D1.11A5), sli-3
Kernel version: 2.6.32-71.el6.x86_64
Reboot 5 times, no lpfc kernel panic came out.
As comment #1 spot out:
>Emulex believes there is exposure to this issue in large SAN environment where
>the device discovery process could see delayed responses which result in iocbs
Do we need a large SAN environment to reproduce this issue?
Please kindly ignore previous update
Verified fixed by Intel
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 therefore 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.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, timing issues could cause the FIP (FCoE Initialization Protocol) FLOGIs to timeout even if there were no problems. This caused the kernel to go into a non-FIP mode even though it should have been in the FIP mode. With this update, the timing issues no longer occur and the kernel no longer switches to the non-FIP mode when logging to the Fibre Channel Switch/Forwarder.