A fix is available
APAR status
Closed as program error.
Error description
readvgda -v3 can stuck in a loop causing snap -L to hang. The procstack command against the looping readvgda will show the stack: 0xd0129fdc free_y(??, ??) + 0x59c 0xd0127770 free_common(??) + 0xb0 0xd051ee54 odm_terminate() + 0x494 0xd051df20 __odm_initfini_fini() + 0x60 0xd0184e44 mod_fini1(??, ??) + 0xa4 0xd0184d30 modfini(??) + 0xf0 0xd01857f4 __modfini() + 0x54 0xd01890b0 exit(??) + 0x1d0 0x10000360 sigsegv_handler(??) + 0x40 <signal> 0xd0129fdc free_y(??, ??) + 0x59c 0xd0127770 free_common(??) + 0xb0 0xd052cde4 raw_find_obj(??, ??, ??) + 0xce4 0xd05211c4 odm_get_obj(??, ??, ??, ??) + 0xc4 0xd0521e30 odm_get_first(??, ??, ??) + 0x70 0x10002258 check_odm@AF24_6(??, ??, ??, ??) + 0x178 0x100079b8 display_svg_q_flag(??) + 0x78 0x100016e8 main(??, ??) + 0x348 0x10000168 __start() + 0x68
Local fix
Kill the looping readvgda process(s)
Problem summary
On certain data on disk, readvgda with certain options may hang if it gets SIGSEGV twice.
Problem conclusion
Better handle the seg fault signal handling so that we cannot hang.
Temporary fix
Comments
APAR Information
APAR number
IV05824
Reported component name
AIX 5.3
Reported component ID
5765G0300
Reported release
530
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Submitted date
2011-08-11
Closed date
2011-08-11
Last modified date
2013-02-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
AIX 5.3
Fixed component ID
5765G0300
Applicable component levels
R530 PSY U844628
UP11/10/10 I 1000
PTF to Fileset Mapping
U844628 bos.rte.lvm 5.3.12.4
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11P","label":"APARs - AIX 5.3 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"530","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
21 February 2013