Bug 165848 - Disable FAN processing in Emulex lpfc driver
Summary: Disable FAN processing in Emulex lpfc driver
Keywords:
Status: CLOSED DUPLICATE of bug 165850
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom Coughlan
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-12 20:37 UTC by Tom Coughlan
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-12 21:09:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tom Coughlan 2005-08-12 20:37:38 UTC
From my rhkernel-list posting on 05 Aug 2005:

Emulex requests the following fix for U6, if possible.

The current driver does not process a particular FC link event properly.
This can cause devices on the FC to become inaccessible.

The details: when an FC initialization event occurs a node can
optionally wait for a Fabric Address Notification (FAN) to arrive from
another node that it was in communication with. If the address
information in the FAN exactly match the values prior to the
initialization, then any existing exchanges can be resumed. If the FAN
does not arrive, or it is ignored, or the address values do not match,
then communication with the the remote node is restarted from scratch
(FLOGI - Fabric Login).

The patch simply ignores the FAN and goes straight to FLOGI. This is
done to keep the fix as simple as possible. The FLOGI path should be
very safe because it is already the default approach used in most other
FC link events.

I built the patched driver and did some regression testing. Emulex has
tested it and has already given it to their big OEMs for qualification.
Taking this patch is the best way for us to keep U6 synchronized with
the rest of the world.

Comment 1 Ernie Petrides 2005-08-12 21:09:03 UTC
Accidental dup of bug 165850.


*** This bug has been marked as a duplicate of 165850 ***


Note You need to log in before you can comment on or make changes to this bug.