Date Added:
Search Keys:
Issue:
Solution:

Date Added: June 21, 2007

The new AIX TL06 (kernel filesets 5.3.0.60) has a change in the pthread scheduling that affects GPFS.

Solution:
GPFS has a fix (596796) for this scheduling problem which will be coming out in the next GPFS maintenance levels 3.1.0.13 and 2.3.0.24. These will be coming out in the next few weeks.

If AIX 5.3 TL06 is already installed, open a Problem Call with GPFS service, who can build an efix for the current GPFS maintenance levels.

For information go to GPFS Forum at http://www.ibm.com/developerworks/forums/dw_forum.jsp?forum=479&cat=13

Date Added: June 20, 2007

TWS LL - An error was introduced in all 32 bit linux ports of TWS LoadLeveler 3.4.1.1 which can cause TWS LoadLeveler jobs to fail.

Users Affected:
All installations that use 32 bit linux ports of TWS LoadLeveler 3.4.1.1.

Issue:
The error causes user process limits to be set to uninitialized values, which can cause application failures.
When the uninitialized value is very small, the user application may terminate abnormally due to exceeding the small limit.

Solution:
Apply apar IZ00385 efix rpms which are available from IBM service for the following platforms:

x86_redhat_4.0.0
x86_redhat_3.0.0
x86_sles_10.0.0
x86_sles_9.0.0

Date Added: June 15, 2007

RSCT - Potential deadlock within certain Resource Managers. This may affect dlpar commands from the HMC GUI.

Users Affected:
Users with rsct.core.rmc 2.3.9.4, rsct.core.rmc 2.3.10.0, rsct.core.rmc 2.4.5.4 or rsct.core.rmc 2.4.6.0

Issue:
A potential deadlock exists within certain Resource Managers. The Resource Managers that are known to possibly be affected are IBM.WLMRM and IBM.HostRM.

Issuing lssrc against these Resource Managers, or lsrsrc against a resource class managed by one of the Resource Managers (e.g. IBM.Program) may hang.

A hang of IBM.HostRM may cause dlpar commands from the HMC GUI to hang. Other symptoms may be lspartition -dlpar and lspartition -spf hanging and lpartition -debug not displaying all of the lpars.

Solution:
Apply IY90698 (rsct.core.rmc 2.3.10.1) or higher.
Apply IY90697 (rsct.core.rmc 2.4.6.1) or higher.

Date Added: June 15, 2007

RSCT - IBM.ConfigRMd core dump after migrating nodes in existing peer domains to RSCT 2.3.11.0 or RSCT 2.4.7.0

Users Affected:
Nodes in a peer domain migrated to rsct.core.rmc 2.3.11.0 or rsct.core.rmc 2.4.7.0.

Issue:
IBM.ConfigRMd will dump core every 24 hours on a node in a peer domain that was migrated to rsct.core.rmc 2.3.11.0 or rsct.core.rmc 2.4.7.0.

IBM.ConfigRM will restart automatically after the core dump.

Solution:
Apply IY99078 (rsct.core.rmc 2.3.11.1) or higher.
Apply IY99077 (rsct.core.rmc 2.4.7.1) or higher.

Date and Time: June 13, 2007
GPFS Maintenance Level incompatibility
For information go to GPFS Forum at http://www.ibm.com/developerworks/forums/dw_forum.jsp?forum=479&cat=13

Date and Time: April 04, 2007
The "smt" keyword is defaulted to "no" under LoadLeveler 3.4.0.0 and 3.4.0.1.

The "smt" keyword is defaulted to "no" under LoadLeveler 3.4.0.0 and 3.4.0.1.
This may cause jobs to have degraded performance if SMT is enabled on machines in
the LoadLeveler cluster.

For more information go to: LL 3.4.0.1 defaults to "SMT=no"