본문 바로가기

카테고리 없음

Via Storx Raid Controller Driver Memory Leak

Printable version
  1. Seagate Raid Controller Driver
  2. Via Storz Raid Controller Driver Memory Leak System
  3. Amd Raid Controller Driver Downloads

* RECOMMENDED * HP ProLiant Smart Array Controller Driver for VMware ESXi 5.0 (Bundle file)

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type:Driver - Storage Controller
Version:5.0.0-40.1(19 Feb 2013)
Operating System(s): VMware ESXi 5.0
File name:hpsa-500-5.0.0-offline_bundle-933277.zip (58 KB)
This bundle file is for updating the HP ProLiant Smart Array driver when creating custom install images with VMware ESXi 5.0.

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added new controller support for Smart Array P822 and Smart Array P721m.
Enabled Rapid Parity initialization support. New feature will keep newly created volumes offline until parity initialization is completed. Driver will periodocally check the device to see if it is ready, and bring it online when the process is complete. Driver will indicate if there are offline volumes in /proc info file and /var/log/vmkernel log files. Feature will be enabled by Smart Array firmware update.

To ensure the integrity of your download, HP recommends verifying your results with this MD5 Checksum value:

hpsa-500-5.0.0-offline_bundle-933277.zipc155464ceb26d320666894ba01b2aad2

Reboot Requirement:
Reboot is required after installation for updates to take effect and hardware stability to be maintained.

Installation:
Bundle file version is strictly for creating custom install images.
If you need to update the driver on a previously installed server, use the VIB format instead.
See instructions for using VMware’s Image Builder in section “Using vSphere ESXi Image Builder CLI” in vSphere Installation and Setup section of vSphere documentation at http://www.vmware.com/support/

End User License Agreements:
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Version:5.0.0.118-1 (21 Apr 2016)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  • Restored paths to a Shared Storage RAID enclosure which was not automatically added.
  • HPE Smart Array Px1x Controllers, which were not supported with HPSA VMware driver versions 5.0.0.114-1 and 5.0.0.116-1, are now fully supported. Please reference CA# c05105304 for more details.

Added support for:
HP Smart Array P542D Controller.
HP Smart Array P240nr Controller.
HP Smart HBA H240nr Controller


Version:5.0.0.116-1 (13 Nov 2015)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

Known Issue:

HPSA Driver bundle version 5.0.0.116-1 for HPE Smart Array Px1x Controllers is not supported on VMware ESXi 5.0. Refer to HPE Customer Advisory #c05105304: http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c05105304, for additional information. Click the Release Notes tab to view a list of HPE Smart Array Controllers that are supported with this driver version.

Enabled operation with third party external RAID enclosures.


Version:5.0.0.114-1 (10 Nov 2015)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  • Implements rescan patches to solve new device rescan issue.
  • Implements changes to abort handler logic to avoid PSOD on aborting an already completed command.

Known Issue:

HPSA Driver bundle version 5.0.0.114-1 for HPE Smart Array Px1x Controllers is not supported on VMware ESXi 5.0. Refer to HPE Customer Advisory #c05105304: http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c05105304, for additional information. Click the Release Notes tab to view a list of HPE Smart Array Controllers that are supported with this driver version.


Version:5.0.0.106-1 (15 Jun 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Restored support for the HP Smart Array P700m Controller.
  • Added support for the HP MSA1040 external RAID enclosure.

Version:5.0.0.84-1 (30 Mar 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Improved SCSI abort request handling.
  • Improved handling of errors during device discovery.
  • HBA mode updates.
  • Performance improvements via driver restructuring to eliminate locking.
  • Support for new HP Smart Array RAID controllers and Smart HBAs.

Version:5.0.0.74-1 (1 Oct 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Performance improvements:

  • The hpsa driver has been extensively refactored for significant performance improvements over previous versions.

Version:5.0.0.60-1 (11 Jun 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

· Fixed a memory leak associated with device rescans resulting in out of memory conditions and a potential PSOD.
· Fixed a null pointer dereference in error handling code that can cause a PSOD in rare cases when device inquiries fail.
· Restore LUN numbering policy to start with 1 instead of 0, avoiding potential issues with Raw Device Maps.
· Enable 64bit DMA mapping instead of default 32bit mapping.
· Improve null pointer checks in device rescanning code, avoiding a potential PSOD.
· Restore maximum outstanding command count, removing artificial limitation that could impact performance.
· Restore support for legacy HP Smart Array P700m controller.


Version:5.0.0-58.1 (18 Feb 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added HPSSD Smart Path feature.
Added support for HP Secure Encryption.
Added additional HP Smart Array Controller Px3x support.
Added support for multiple ioqueues.


Version:5.0.0-44.1 (7 Nov 2013)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added support for HP Smart Array Px3x Controllers.


Version:5.0.0-40.1 (19 Feb 2013)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added new controller support for Smart Array P822 and Smart Array P721m.
Enabled Rapid Parity initialization support. New feature will keep newly created volumes offline until parity initialization is completed. Driver will periodocally check the device to see if it is ready, and bring it online when the process is complete. Driver will indicate if there are offline volumes in /proc info file and /var/log/vmkernel log files. Feature will be enabled by Smart Array firmware update.


Version:5.0.0-28.0 (4 Sep 2012)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  1. Add support for correctly displaying RAID 1(ADM) mode for logical volumes. Formerly, RAID 1(ADM) volumes were incorrectly displayed as RAID UNKNOWN.
  2. Remove code that limited the number of external target (array) device connections to 8 array ports. Exceeding 8 ports prevented logical volumes from registering with the driver. Improved code handling paths and targets.

Type:Driver - Storage Controller
Version:5.0.0-40.1(19 Feb 2013)
Operating System(s):
VMware ESXi 5.0

Description

This bundle file is for updating the HP ProLiant Smart Array driver when creating custom install images with VMware ESXi 5.0.

Enhancements

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added new controller support for Smart Array P822 and Smart Array P721m.
Enabled Rapid Parity initialization support. New feature will keep newly created volumes offline until parity initialization is completed. Driver will periodocally check the device to see if it is ready, and bring it online when the process is complete. Driver will indicate if there are offline volumes in /proc info file and /var/log/vmkernel log files. Feature will be enabled by Smart Array firmware update.

Installation Instructions

To ensure the integrity of your download, HP recommends verifying your results with this MD5 Checksum value:

hpsa-500-5.0.0-offline_bundle-933277.zipc155464ceb26d320666894ba01b2aad2

Reboot Requirement:
Reboot is required after installation for updates to take effect and hardware stability to be maintained.

Installation:
Bundle file version is strictly for creating custom install images.
If you need to update the driver on a previously installed server, use the VIB format instead.
See instructions for using VMware’s Image Builder in section “Using vSphere ESXi Image Builder CLI” in vSphere Installation and Setup section of vSphere documentation at http://www.vmware.com/support/

Release Notes

End User License Agreements:
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Revision History

Version:5.0.0.118-1 (21 Apr 2016)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  • Restored paths to a Shared Storage RAID enclosure which was not automatically added.
  • HPE Smart Array Px1x Controllers, which were not supported with HPSA VMware driver versions 5.0.0.114-1 and 5.0.0.116-1, are now fully supported. Please reference CA# c05105304 for more details.

Added support for:
HP Smart Array P542D Controller.
HP Smart Array P240nr Controller.
HP Smart HBA H240nr Controller


Version:5.0.0.116-1 (13 Nov 2015)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

Known Issue:

HPSA Driver bundle version 5.0.0.116-1 for HPE Smart Array Px1x Controllers is not supported on VMware ESXi 5.0. Refer to HPE Customer Advisory #c05105304: http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c05105304, for additional information. Click the Release Notes tab to view a list of HPE Smart Array Controllers that are supported with this driver version.

Enabled operation with third party external RAID enclosures.


Version:5.0.0.114-1 (10 Nov 2015)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  • Implements rescan patches to solve new device rescan issue.
  • Implements changes to abort handler logic to avoid PSOD on aborting an already completed command.

Known Issue:

HPSA Driver bundle version 5.0.0.114-1 for HPE Smart Array Px1x Controllers is not supported on VMware ESXi 5.0. Refer to HPE Customer Advisory #c05105304: http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c05105304, for additional information. Click the Release Notes tab to view a list of HPE Smart Array Controllers that are supported with this driver version.


Version:5.0.0.106-1 (15 Jun 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Restored support for the HP Smart Array P700m Controller.
  • Added support for the HP MSA1040 external RAID enclosure.

Version:5.0.0.84-1 (30 Mar 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Improved SCSI abort request handling.
  • Improved handling of errors during device discovery.
  • HBA mode updates.
  • Performance improvements via driver restructuring to eliminate locking.
  • Support for new HP Smart Array RAID controllers and Smart HBAs.

Version:5.0.0.74-1 (1 Oct 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Performance improvements:

  • The hpsa driver has been extensively refactored for significant performance improvements over previous versions.

Version:5.0.0.60-1 (11 Jun 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

· Fixed a memory leak associated with device rescans resulting in out of memory conditions and a potential PSOD.
· Fixed a null pointer dereference in error handling code that can cause a PSOD in rare cases when device inquiries fail.
· Restore LUN numbering policy to start with 1 instead of 0, avoiding potential issues with Raw Device Maps.
· Enable 64bit DMA mapping instead of default 32bit mapping.
· Improve null pointer checks in device rescanning code, avoiding a potential PSOD.
· Restore maximum outstanding command count, removing artificial limitation that could impact performance.
· Restore support for legacy HP Smart Array P700m controller.


Version:5.0.0-58.1 (18 Feb 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added HPSSD Smart Path feature.
Added support for HP Secure Encryption.
Added additional HP Smart Array Controller Px3x support.
Added support for multiple ioqueues.


Version:5.0.0-44.1 (7 Nov 2013)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added support for HP Smart Array Px3x Controllers.


Version:5.0.0-40.1 (19 Feb 2013)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Added new controller support for Smart Array P822 and Smart Array P721m.
Enabled Rapid Parity initialization support. New feature will keep newly created volumes offline until parity initialization is completed. Driver will periodocally check the device to see if it is ready, and bring it online when the process is complete. Driver will indicate if there are offline volumes in /proc info file and /var/log/vmkernel log files. Feature will be enabled by Smart Array firmware update.


Version:5.0.0-28.0 (4 Sep 2012)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  1. Add support for correctly displaying RAID 1(ADM) mode for logical volumes. Formerly, RAID 1(ADM) volumes were incorrectly displayed as RAID UNKNOWN.
  2. Remove code that limited the number of external target (array) device connections to 8 array ports. Exceeding 8 ports prevented logical volumes from registering with the driver. Improved code handling paths and targets.

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

Show Table of Contents
kernel component, BZ#1019091

Dear developers, I face a memory leak problem in nVidia driver. Environment: Windows7 64bit Quadro5000 CUDA GPU COMPUTING SDK 4.0 Driver ver.296.70 Memory leak happens when you call the function clReleaseMemObject() after calling clCreateBuffer(). And here is a sample code to verify that memory leak appers. Using PoolMon to Find a Kernel-Mode Memory Leak.; 2 minutes to read Contributors. In this article. If you suspect there is a kernel-mode memory leak, the easiest way to determine which pool tag is associated with the leak is to use the PoolMon tool. But I find it strange that a WHQL-certified network driver, that is pushed officially through Windows Update, and even included on the Windows 10 TH2 install media, can leak memory. As far as I know, it wouldn't pass WHQL certification if it leak memory.

Possible Memory leak in nVidia driver If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. IBM ServeRAID MR10ie (CIOv) SAS controller (46C7167) IBM ServeRAID MR10i SAS controller (43W4296) IBM ServeRAID MR10k SAS controller (43W4280) IBM ServeRAID MR10M SAS controller (43W4339) MegaRAID 8480 SAS controller (39R8850) Fixes. Modified MSM to get IR controller Minimum physical drive support RAID 0 from the controller firmware.

The following RAID controller cards are no longer supported. However, the aacraid driver still detects them. Thus, they are marked as not supported in the dmesg output.
  • PERC 3/Di (Opal/PERC3Di)
  • PERC 3/Di (Iguana FlipChip/PERC3DiF)
  • PERC 3/Di (Lexus/PERC3DiL)
  • PERC 3/Di (Dagger/PERC3DiD)
  • Adaptec 2120S (Crusader)
  • Adaptec 2200S (Vulcan-2m)
  • Legend S230 (Legend Vulcan)
  • Adaptec 3240S (Tornado)
  • ASR-2025ZCR SCSI SO-DIMM PCI-X ZCR (Terminator)
  • ASR-2130S (Lancer)
  • AAR-2620SA (Intruder)
  • ICP9024RO (Lancer)
  • ICP9047MA (Lancer)
  • ICP5445AU (Hurricane44)
  • ICP5085BR (Marauder-E)
  • Themisto Jupiter Platform
  • ASR-2020SA SATA PCI-X ZCR (Skyhawk)
  • AAR-2410SA PCI SATA 4ch (Jaguar II)
  • AAR-2810SA PCI SATA 8ch (Corsair-8)
  • ESD SO-DIMM PCI-X SATA ZCR (Prowler)
  • ASR-2240S (SabreExpress)
  • ASR-4800SAS (Marauder-X)
  • ASR-3800 (Hurricane44)
  • Dell PERC2/QC
The following cards detected by aacraid are also no longer supported but they are not identified as not supported in the dmesg output:
  • IBM 8i (AvonPark Lite)
  • IBM 8k/8k-l4 (Aurora Lite)
Note that the Kdump mechanism might not work properly on the aforementioned RAID controllers.
kernel component, BZ#1061210
When the hpsa_allow_any option is used, the hpsa driver allows the use of PCI IDs that are not listed in the driver's pci-id table. Thus, cards detected when this option is used, are not supported in Red Hat Enterprise Linux 7.
kernel component, BZ#975791
The following cciss controllers are no longer supported:
  • Smart Array 5i
  • Smart Array 5312
  • Smart Array 642
  • Smart Array 6400 EM
  • Smart Array P600
  • Smart Array P400
  • Smart Array E200i
  • Smart Array E500
kernel component, BZ#1055089
The systemd service does not spawn the getty tool on the /dev/hvc0/virtio console if the virtio console driver is not found before loading kernel modules at system startup. As a consequence, a TTY terminal does not start automatically after the system boot when the system is running as a KVM guest. To work around this problem, start getty on /dev/hvc0/ after the system boot. The ISA serial device, which is used more commonly, works as expected.
kernel component, BZ#1060565
Memory
A previously applied patch is causing a memory leak when creating symbolic links over NFS. Consequently, if creating a very large number of symbolic links, on a scale of hundreds of thousands, the system may report the out of memory status.

Seagate Raid Controller Driver

Raid
kernel component, BZ#1097468
The Linux kernel Non-Uniform Memory Access (NUMA) balancing does not always work correctly in Red Hat Enterprise Linux 7. As a consequence, when the numa_balancing parameter is set, some of the memory can move to an arbitrary non-destination node before moving to the constrained nodes, and the memory on the destination node also decreases under certain circumstances. There is currently no known workaround available.
kernel component, BZ#915855
The QLogic 1G iSCSI Adapter present in the system can cause a call trace error when the qla4xx driver is sharing the interrupt line with the USB sub-system. This error has no impact on the system functionality. The error can be found in the kernel log messages located in the /var/log/messages file. To prevent the call trace from logging into the kernel log messages, add the nousb kernel parameter when the system is booting.
system-config-kdump component, BZ#1077470

Via Storz Raid Controller Driver Memory Leak System

In the Kernel Dump Configuration window, selecting the Raw device option in the Target settings tab does not work. To work around this problem, edit the kdump.conf file manually.
kernel component, BZ#1087796
An attempt to remove the bnx2x module while the bnx2fc driver is processing a corrupted frame causes a kernel panic. To work around this problem, shut down any active FCoE interfaces before executing the modprobe -r bnx2x command.
kexec-tools component, BZ#1089788

Amd Raid Controller Driver Downloads

Due to a wrong buffer size calculation in the makedumpfile utility, an OOM error could occur with a high probability. As a consequence, the vmcore file cannot be captured under certain circumstances. No workaround is currently available.