AIX71 TL05 PTF in Error (Doc Number=6209)

Fix Readme

Abstract

AIX71 TL05 PTF in Error (Doc Number=6209) PTF: U879852
Fileset: devices.fcp.disk.rte.7.1.5.16
APAR: IJ08271 reported against fix pack: 7100-05-02-1832
Fix not yet available
There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size. PTF: U879851
Fileset: devices.fcp.tape.rte.7.1.5.17
APAR: IJ08271 reported against fix pack: 7100-05-02-1832
Fix not yet available
There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size. PTF: U879850
Fileset: devices.scsi.disk.rte.7.1.5.17
APAR: IJ08271 reported against fix pack: 7100-05-02-1832
Fix not yet available
There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size. PTF: U876602
Fileset: devices.fcp.tape.rte.7.1.5.16
APAR: IJ08271 reported against fix pack: 7100-05-02-1810
Fix not yet available
There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size. PTF:

Content

PTF: U879852

Fileset: devices.fcp.disk.rte.7.1.5.16

APAR: IJ08271 reported against fix pack: 7100-05-02-1832

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U879851

Fileset: devices.fcp.tape.rte.7.1.5.17

APAR: IJ08271 reported against fix pack: 7100-05-02-1832

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U879850

Fileset: devices.scsi.disk.rte.7.1.5.17

APAR: IJ08271 reported against fix pack: 7100-05-02-1832

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U876602

Fileset: devices.fcp.tape.rte.7.1.5.16

APAR: IJ08271 reported against fix pack: 7100-05-02-1810

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U876601

Fileset: devices.scsi.disk.rte.7.1.5.16

APAR: IJ08271 reported against fix pack: 7100-05-02-1810

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U875900

Fileset: devices.fcp.disk.rte.7.1.5.15

APAR: IJ08271 reported against fix pack: 7100-05-02-1810

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U873235

Fileset: devices.fcp.tape.rte.7.1.5.0

APAR: IJ08271 reported against fix pack: 7100-05

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U873218

Fileset: devices.fcp.disk.rte.7.1.5.0

APAR: IJ08271 reported against fix pack: 7100-05

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U873217

Fileset: devices.scsi.disk.rte.7.1.5.0

APAR: IJ08271 reported against fix pack: 7100-05

Fix not yet available

There is a small chance of a system crash occurring when changing the RAS trace settings for the scsidiskdd.mpio component (such as by using the ctctrl command), especially for suspending the trace or changing the trace buffer size.

PTF: U875755

Fileset: bos.sysmgt.trace.7.1.5.15

APAR: IJ08146 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

probevue command core dumps when it tries to find the scope of expression (a+b) while verifying assignment compatibility.

PTF: U872166

Fileset: bos.sysmgt.trace.7.1.5.0

APAR: IJ08146 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

probevue command core dumps when it tries to find the scope of expression (a+b) while verifying assignment compatibility.

PTF: U879852

Fileset: devices.fcp.disk.rte.7.1.5.16

APAR: IJ07842 reported against fix pack: 7100-05-02-1832

Fix available in fixpack: 7100-05-03-1838

Possible I/O error when all paths to a storage device are down for a short time, such as during a DS8k warmstart.  AIX sometimes fails I/O if all paths to the storage device became unusable for approximately 15 seconds.  This error is known to be possible with DS8k when running SDD PCM; other configurations may be exposed as well.

PTF: U875900

Fileset: devices.fcp.disk.rte.7.1.5.15

APAR: IJ07842 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

Possible I/O error when all paths to a storage device are down for a short time, such as during a DS8k warmstart.  AIX sometimes fails I/O if all paths to the storage device became unusable for approximately 15 seconds.  This error is known to be possible with DS8k when running SDD PCM; other configurations may be exposed as well.

PTF: U873218

Fileset: devices.fcp.disk.rte.7.1.5.0

APAR: IJ07842 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

Possible I/O error when all paths to a storage device are down for a short time, such as during a DS8k warmstart.  AIX sometimes fails I/O if all paths to the storage device became unusable for approximately 15 seconds.  This error is known to be possible with DS8k when running SDD PCM; other configurations may be exposed as well.

PTF: U875873

Fileset: bos.alt_disk_install.rte.7.1.5.15

APAR: IJ07427 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

Below grep usage are displayed during the nimadm mksysb to mksysb migration:  # nimadm -T pvc7-mksysb -O /nim/mksysb/pvc7-mksysb_72 -s spot72 -l lpp72 -j nimvg -Y -N pvc7-mksysb_72  Initializing the NIM master.  Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p [parasep]] -e pattern_list... [-f pattern_file...] [file...] Usage: grep [-r] [-R] [-H] [-L]  [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p [parasep]] [-e pattern_list...] -f pattern_file... [file...] Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p [parasep]] pattern_list [file...]

PTF: U870545

Fileset: bos.alt_disk_install.rte.7.1.5.0

APAR: IJ07427 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

Below grep usage are displayed during the nimadm mksysb to mksysb migration:  # nimadm -T pvc7-mksysb -O /nim/mksysb/pvc7-mksysb_72 -s spot72 -l lpp72 -j nimvg -Y -N pvc7-mksysb_72  Initializing the NIM master.  Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p [parasep]] -e pattern_list... [-f pattern_file...] [file...] Usage: grep [-r] [-R] [-H] [-L]  [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p [parasep]] [-e pattern_list...] -f pattern_file... [file...] Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p [parasep]] pattern_list [file...]

PTF: U875893

Fileset: devices.vdevice.IBM.l-lan.rte.7.1.5.15

APAR: IJ07165 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

Running entstat command on a virtual ethernet port will show stale ndd_2_flags (or those flags may be missing, if first time enstat is run on the port) in the "Driver Flags" section of the entstat output.  ndd_2_flags include VIOENT, IPV6_LSO, VIRTUAL_PORT, PHYS_LINK_UP, etc.

PTF: U870549

Fileset: devices.vdevice.IBM.l-lan.rte.7.1.5.0

APAR: IJ07165 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

Running entstat command on a virtual ethernet port will show stale ndd_2_flags (or those flags may be missing, if first time enstat is run on the port) in the "Driver Flags" section of the entstat output.  ndd_2_flags include VIOENT, IPV6_LSO, VIRTUAL_PORT, PHYS_LINK_UP, etc.

PTF: U876611

Fileset: bos.rte.libc.7.1.5.16

APAR: IJ06228 reported against fix pack: 7100-05-02-1810

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U876610

Fileset: bos.64bit.7.1.5.16

APAR: IJ06228 reported against fix pack: 7100-05-02-1810

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U876609

Fileset: bos.adt.prof.7.1.5.16

APAR: IJ06228 reported against fix pack: 7100-05-02-1810

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U875843

Fileset: bos.rte.shell.7.1.5.15

APAR: IJ06228 reported against fix pack: 7100-05-02-1810

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U875840

Fileset: bos.rte.control.7.1.5.15

APAR: IJ06228 reported against fix pack: 7100-05-02-1810

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U874942

Fileset: bos.rte.libc.7.1.5.17

APAR: IJ06228 reported against fix pack: 7100-05-02-1832

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U874941

Fileset: bos.64bit.7.1.5.17

APAR: IJ06228 reported against fix pack: 7100-05-02-1832

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U874940

Fileset: bos.rte.shell.7.1.5.16

APAR: IJ06228 reported against fix pack: 7100-05-02-1832

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U874939

Fileset: bos.adt.prof.7.1.5.17

APAR: IJ06228 reported against fix pack: 7100-05-02-1832

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U874938

Fileset: bos.rte.control.7.1.5.16

APAR: IJ06228 reported against fix pack: 7100-05-02-1832

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U870546

Fileset: bos.64bit.7.1.5.0

APAR: IJ06228 reported against fix pack: 7100-05

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U870520

Fileset: bos.rte.control.7.1.5.0

APAR: IJ06228 reported against fix pack: 7100-05

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U870519

Fileset: bos.adt.prof.7.1.5.0

APAR: IJ06228 reported against fix pack: 7100-05

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U870518

Fileset: bos.rte.libc.7.1.5.0

APAR: IJ06228 reported against fix pack: 7100-05

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U870515

Fileset: bos.rte.shell.7.1.5.0

APAR: IJ06228 reported against fix pack: 7100-05

Fix not yet available

A hang may occur in a multithreaded process that is  forking child processes.  One thread will be seen hung in _atfork_prepare:  [0010B7B0]e_block_thread+000290 () [001B8A40]nsleep_com+0000C0 (??) [001B9864]nsleep+000064 (??, ??) [00003938]syscall+000230 () [90000000058090C]_p_nsleep+00000C (??, ??) [900000000039564]nsleep+0000E4 (??, ??) [900000000038F54]usleep+0000D4 (??) [90000000003F780]_libc_pre_fork+000260 () [90000000058D13C]_atfork_prepare+0001BC () [90000000010F63C]__fork+00003C ()  Whereas another will likely be seen waiting on a rwlock:  [90000000057B840]_event_sleep+000580 (??, ??, ??, ??,  ??, ??) [90000000057C344]_event_wait+000344 (??, ??) [900000000590270]_rwlock_wait_local+000110 (??, ??, ??) [90000000059010C]_rwlock_wait+0000AC (??, ??, ??) [900000000590ED4]_rwlock_wrlock+0002B4 (??, ??, ??) [90000000006F144]method_getentry+000204 (??, ??, ??, ??, ??) [900000000085488]__method_getentry_v2+0001A8 (??, ??, ??, ??, ??, ??) [9000000000F331C]process_module+00019C (??, ??, ??, ?? , ??) [9000000000F4218]getconfattrs+0006B8 (??, ??, ??) [9000000000F47C0]getconfattr+000260 (??, ??, ??, ??) [900000000088A78]getuserattrs+001998 (??, ??, ??) [9000000000F7658]getuserattr+000338 (??, ??, ??, ??) [9000000001F1ECC]loginsuccess+0000CC (??, ??, ??, ??)

PTF: U879832

Fileset: bos.rte.cron.7.1.5.16

APAR: IJ06138 reported against fix pack: 7100-05-02-1832

Fix available in fixpack: 7100-05-03-1838

If at jobs have been submitted before a system update (to 7.1tl5, 7.2tl2, or 6.1tl9-sp10), but are not scheduled to run until after the update, they will fail  to run due to a change in at job naming convention.

PTF: U871959

Fileset: bos.rte.cron.7.1.5.0

APAR: IJ06138 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

If at jobs have been submitted before a system update (to 7.1tl5, 7.2tl2, or 6.1tl9-sp10), but are not scheduled to run until after the update, they will fail  to run due to a change in at job naming convention.

PTF: U875882

Fileset: bos.rte.security.7.1.5.15

APAR: IJ06137 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

Incorrect behaviour of chsec command was observed in operations described below: User with privileged permission is still able to assign ldap groups to both root as well as local user, even when domainlessgroup attribute was disabled in AIX. This is a legacy issue because the incorrect behaviour was also observed in oslevels where domainlessgroup feature was unavailable.

PTF: U874937

Fileset: bos.rte.security.7.1.5.16

APAR: IJ06137 reported against fix pack: 7100-05-02-1832

Fix available in fixpack: 7100-05-03-1838

Incorrect behaviour of chsec command was observed in operations described below: User with privileged permission is still able to assign ldap groups to both root as well as local user, even when domainlessgroup attribute was disabled in AIX. This is a legacy issue because the incorrect behaviour was also observed in oslevels where domainlessgroup feature was unavailable.

PTF: U875784

Fileset: bos.aixpert.cmds.7.1.5.15

APAR: IJ06134 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

Incorrect output from aixpert

PTF: U870528

Fileset: bos.aixpert.cmds.7.1.5.0

APAR: IJ06134 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

Incorrect output from aixpert

PTF: U879852

Fileset: devices.fcp.disk.rte.7.1.5.16

APAR: IJ06128 reported against fix pack: 7100-05-02-1832

Fix not yet available

If the disks on AIX are using ODM that does not specify LUN Reset support, there is a chance that a disk I/O error may occur after certain SAN fabric errors (such as cable pulls). All disk ODM supplied with AIX has LUN Reset support turned on, so this risk of I/O error only occurs when using third party ODM, if that third party ODM does not specify LUN reset support.

PTF: U875900

Fileset: devices.fcp.disk.rte.7.1.5.15

APAR: IJ06128 reported against fix pack: 7100-05-02-1810

Fix not yet available

If the disks on AIX are using ODM that does not specify LUN Reset support, there is a chance that a disk I/O error may occur after certain SAN fabric errors (such as cable pulls). All disk ODM supplied with AIX has LUN Reset support turned on, so this risk of I/O error only occurs when using third party ODM, if that third party ODM does not specify LUN reset support.

PTF: U875864

Fileset: devices.pci.77102224.com.7.1.5.15

APAR: IJ06128 reported against fix pack: 7100-05-02-1810

Fix not yet available

If the disks on AIX are using ODM that does not specify LUN Reset support, there is a chance that a disk I/O error may occur after certain SAN fabric errors (such as cable pulls). All disk ODM supplied with AIX has LUN Reset support turned on, so this risk of I/O error only occurs when using third party ODM, if that third party ODM does not specify LUN reset support.

PTF: U875860

Fileset: devices.pci.df1000f7.com.7.1.5.15

APAR: IJ06128 reported against fix pack: 7100-05-02-1810

Fix not yet available

If the disks on AIX are using ODM that does not specify LUN Reset support, there is a chance that a disk I/O error may occur after certain SAN fabric errors (such as cable pulls). All disk ODM supplied with AIX has LUN Reset support turned on, so this risk of I/O error only occurs when using third party ODM, if that third party ODM does not specify LUN reset support.

PTF: U873220

Fileset: devices.pci.df1000f7.com.7.1.5.0

APAR: IJ06128 reported against fix pack: 7100-05

Fix not yet available

If the disks on AIX are using ODM that does not specify LUN Reset support, there is a chance that a disk I/O error may occur after certain SAN fabric errors (such as cable pulls). All disk ODM supplied with AIX has LUN Reset support turned on, so this risk of I/O error only occurs when using third party ODM, if that third party ODM does not specify LUN reset support.

PTF: U873218

Fileset: devices.fcp.disk.rte.7.1.5.0

APAR: IJ06128 reported against fix pack: 7100-05

Fix not yet available

If the disks on AIX are using ODM that does not specify LUN Reset support, there is a chance that a disk I/O error may occur after certain SAN fabric errors (such as cable pulls). All disk ODM supplied with AIX has LUN Reset support turned on, so this risk of I/O error only occurs when using third party ODM, if that third party ODM does not specify LUN reset support.

PTF: U870547

Fileset: devices.pci.77102224.com.7.1.5.0

APAR: IJ06128 reported against fix pack: 7100-05

Fix not yet available

If the disks on AIX are using ODM that does not specify LUN Reset support, there is a chance that a disk I/O error may occur after certain SAN fabric errors (such as cable pulls). All disk ODM supplied with AIX has LUN Reset support turned on, so this risk of I/O error only occurs when using third party ODM, if that third party ODM does not specify LUN reset support.

PTF: U875893

Fileset: devices.vdevice.IBM.l-lan.rte.7.1.5.15

APAR: IJ05909 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

System with >128 VEA adapters assigned crashed with:  CRASH INFORMATION: CPU 0 CSA F00000002FF47600 at time of crash, error code for LEDs: 70000000 pvthread+08CD00 STACK: WARNING: bad IAR: 00000000, display stack from LR: 05FAE8A8 [05FAE8A8]netinet:send_clic_init+000128 () [05ED53D4]netinet:config_inet+002F74 (??, ??) [007A6178]IPRA.$config_kmod+0000D8 (??, ??, ??) [007A6F74]sysconfig+000194 (??, ??, ??) [00003930]syscall+000228 () [kdb_get_virtual_memory] no real storage @ 2FF225E8 [10001378]10001378 () [kdb_read_mem] no real storage @ FFFFFFFFFFF5B50  (0)> dd num_dr_handlers num_dr_handlers+000000: 00000080F1000B00 00200B0000000001  ......... ......

PTF: U870549

Fileset: devices.vdevice.IBM.l-lan.rte.7.1.5.0

APAR: IJ05909 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

System with >128 VEA adapters assigned crashed with:  CRASH INFORMATION: CPU 0 CSA F00000002FF47600 at time of crash, error code for LEDs: 70000000 pvthread+08CD00 STACK: WARNING: bad IAR: 00000000, display stack from LR: 05FAE8A8 [05FAE8A8]netinet:send_clic_init+000128 () [05ED53D4]netinet:config_inet+002F74 (??, ??) [007A6178]IPRA.$config_kmod+0000D8 (??, ??, ??) [007A6F74]sysconfig+000194 (??, ??, ??) [00003930]syscall+000228 () [kdb_get_virtual_memory] no real storage @ 2FF225E8 [10001378]10001378 () [kdb_read_mem] no real storage @ FFFFFFFFFFF5B50  (0)> dd num_dr_handlers num_dr_handlers+000000: 00000080F1000B00 00200B0000000001  ......... ......

PTF: U876603

Fileset: bos.mp64.7.1.5.16

APAR: IJ02779 reported against fix pack: 7100-05-02-1810

Fix available in fixpack: 7100-05-03-1838

find /proc > /dev/null  find: 0652-019 The status on /proc/11993324/fd/5 is not valid. find: 0652-019 The status on /proc/11993324/fd/6 is not valid. find: 0652-019 The status on /proc/11993324/fd/7 is not valid.

PTF: U874935

Fileset: bos.mp64.7.1.5.17

APAR: IJ02779 reported against fix pack: 7100-05-02-1832

Fix available in fixpack: 7100-05-03-1838

find /proc > /dev/null  find: 0652-019 The status on /proc/11993324/fd/5 is not valid. find: 0652-019 The status on /proc/11993324/fd/6 is not valid. find: 0652-019 The status on /proc/11993324/fd/7 is not valid.

PTF: U870555

Fileset: bos.mp64.7.1.5.0

APAR: IJ02779 reported against fix pack: 7100-05

Fix available in fixpack: 7100-05-03-1838

find /proc > /dev/null  find: 0652-019 The status on /proc/11993324/fd/5 is not valid. find: 0652-019 The status on /proc/11993324/fd/6 is not valid. find: 0652-019 The status on /proc/11993324/fd/7 is not valid.

PTF: U876611

Fileset: bos.rte.libc.7.1.5.16

APAR: IJ02777 reported against fix pack: 7100-05-02-1810

Fix not yet available

Usage of NIS could cause memory corruption - this could cause a core dump or other problems in any number of  places. One issue that has been observed is that the IIB DataFlowEngine process can get hung in its createJVM  processes, looping and consuming CPU.

PTF: U876610

Fileset: bos.64bit.7.1.5.16

APAR: IJ02777 reported against fix pack: 7100-05-02-1810

Fix not yet available

Usage of NIS could cause memory corruption - this could cause a core dump or other problems in any number of  places. One issue that has been observed is that the IIB DataFlowEngine process can get hung in its createJVM  processes, looping and consuming CPU.

PTF: U876609

Fileset: bos.adt.prof.7.1.5.16

APAR: IJ02777 reported against fix pack: 7100-05-02-1810

Fix not yet available

Usage of NIS could cause memory corruption - this could cause a core dump or other problems in any number of  places. One issue that has been observed is that the IIB DataFlowEngine process can get hung in its createJVM  processes, looping and consuming CPU.

PTF: U875882

Fileset: bos.rte.security.7.1.5.15

APAR: IJ02777 reported against fix pack: 7100-05-02-1810

Fix not yet available

Usage of NIS could cause memory corruption - this could cause a core dump or other problems in any number of  places. One issue that has been observed is that the IIB DataFlowEngine process can get hung in its createJVM  processes, looping and consuming CPU.

PTF: U875843

Fileset: bos.rte.shell.7.1.5.15

APAR: IJ02777 reported against fix pack: 7100-05-02-1810

Fix not yet available

Usage of NIS could cause memory corruption - this could cause a core dump or other problems in any number of  places. One issue that has been observed is that the IIB DataFlowEngine process can get hung in its createJVM  processes, looping and consuming CPU.

PTF: U875840

Fileset: bos.rte.control.7.1.5.15

APAR: IJ02777 reported against fix pack: 7100-05-02-1810

Fix not yet available

Usage of NIS could cause memory corruption - this could cause a core dump or other problems in any number of  places. One issue that has been observed is that the IIB DataFlowEngine process can get hung in its createJVM  processes, looping and consuming CPU.

PTF: U874942

Fileset: bos.rte.libc.7.1.5.17