Red Hat Bugzilla – Bug 608801
[Emulex 5.6 bug] be2iscsi: IO stalls if any SGE size=65536
Last modified: 2011-01-13 16:39:56 EST
Description of problem:
The IO's will stall if SGE size in any SGL becomes equal to 65536.
Version-Release number of selected component (if applicable):
Every time any SGE size becomes equal to 65536
Steps to Reproduce:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
How often does this condition occur? Trying to narrow down the patchset for the DUP, and hopefully this shouldn't be required. Laurie?
We had not hit this problem before but in RHEL6 Snapshot6, we see it instantaneously. The IO tests stalls almost immediately.
The FIX is a one line change. Hope it can be added to RHEL6.0 (and RHEl5.6)
(In reply to comment #3)
> We had not hit this problem before but in RHEL6 Snapshot6, we see it
> instantaneously. The IO tests stalls almost immediately.
> The FIX is a one line change. Hope it can be added to RHEL6.0 (and RHEl5.6)
In which 6.0 bugzilla did you report this?
The bug for RHEL6.0
The patch that is under discussion is referenced below. There is no change
for the driver version remains same 2.0.527.0. There is no other change required
This bugzilla, proposed for RHEL 5.6, is also requested to be included in the be2iscsi DUP for 5.5.z based on comments from Emulex and mchristi.
You can download this test kernel from http://people.redhat.com/jwilson/el5
Detailed testing feedback is always welcomed.
The io issue of SGE size = 64K is fixed and verified
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.