Description of problem:
Running I/O on RHEL 3.0 and using the v6.06.00b11 driver, the driver
ran out of memory and the OS began arbitrarily killing processes.
The systems had to be rebooted.
Version-Release number of selected component (if applicable):
RHEL 3.0 32-bit v2.21-4.0.1.EL, v2.4.21-9.EL
Sometimes, but not always.
Steps to Reproduce:
Run I/O on a RHEL 3.0 system using the default v6.06.00b11 driver.
The driver will sometimes run out of memory and the OS will begin
arbitrarily killing processes. The system had to be rebooted.
The driver should not run out of memory and should not cause
processes to be killed or force a system reboot.
Request that the v6.07.00 driver be used instead as it resolves
We are planning to update the Qlofic driver in U2/U4. We will need
you to test the beta version of this release to confirm the fix.
WIll do. Are you planning to use the v6.07.01 driver from QLogic
that includes the v3.02.00 firmware for the QLA23xx HBAs?
This problem was fixed with the upgrade of the QLogic driver to
version 6.07.10 in RHEL3 U2 in kernel version 2.4.21-9.14.EL.
ahhh...versioning nightmare. Heather, do you know how 6.07.10 and
the 6.07.02 driver you recently sent me differ?
The version in RHEL 3 U2 is 6.07.02, plus some RH enhancements. It is
not 6.07.10 (there is no such thing as of yet, AFAIK). Sorry for the
Gary, Heather, I would like to work with you to confirm that the the
new driver fixes the several bugzillas you have open, and to certify
RHEL 3 U2 in general. The beta will be available soon.
Ok, but to me it would seem better if 6.07.02 + RH enhancements =
We are having the same problem, however we don't have any QLA HBAs.
We are running InterSystems CachÃ© 5, RHEL 3 (Kernel 2.4.21-9.0.1EL)
on a 4-way Xeon MP 2.8GHz system, with 8GB RAM. Database is over a
An errata 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 the 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.