Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 641457 - FCoE: Do not fall back to non-FIP FLOGI [rhel-6.0.z]
FCoE: Do not fall back to non-FIP FLOGI [rhel-6.0.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.1
All Linux
urgent Severity high
: rc
: 6.1
Assigned To: Frantisek Hrbata
Storage QE
: OtherQA, ZStream
Depends On: 636233
Blocks:
  Show dependency tree / graph
 
Reported: 2010-10-08 14:56 EDT by Benjamin Kahn
Modified: 2010-11-11 07:01 EST (History)
20 users (show)

See Also:
Fixed In Version: kernel-2.6.32-71.4.1.el6
Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-10 14:11:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0842 normal SHIPPED_LIVE Important: kernel security and bug fix update 2010-11-22 14:34:20 EST

  None (edit)
Description Benjamin Kahn 2010-10-08 14:56:40 EDT 
This bug has been copied from bug #636233 and has been proposed
to be backported to 6.0 z-stream (EUS).
Comment 3 Frantisek Hrbata 2010-10-12 14:53:35 EDT 
in kernel-2.6.32-71.4.1.el6
Comment 5 Gris Ge 2010-10-15 03:18:28 EDT 
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
>being queued.

Do we need a large SAN environment to reproduce this issue?
Comment 6 Gris Ge 2010-10-15 03:22:13 EDT 
Please kindly ignore previous update
Comment 9 Jack Morgan 2010-10-26 20:54:02 EDT 
Verified fixed by Intel
Comment 11 errata-xmlrpc 2010-11-10 14:11:02 EST 
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.

http://rhn.redhat.com/errata/RHSA-2010-0842.html
Comment 12 Martin Prpič 2010-11-11 07:01:26 EST 
    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.
    
    New Contents:
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.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.