IBM Support

IV50530: SYSTEM MAY CRASH IN BMINODEFLUSH@AF122_68 APPLIES TO AIX 6100-09

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • System may crash with a stack trace:
    (40)> f
    pvthread+4B0600 STACK:
    [0017E120]bmInodeFlush@AF122_68+000700 (0000000000000000,
     0000000000000280, F1000A200014A000, 0000000003060983,
     0000000000000000, 0000000002C20000, 0000000000000004,
     0000000003060983 [??])
    [0017A138]bmInodeFlush+000038 (??)
    [003704EC]pagerUnbind@AF66_41+00012C (??, ??, ??, ??)
    [0036F5CC]pagerUnbind+00002C (??, ??, ??)
    [001707A8]iRecycle+000128 (??, ??, ??)
    [0016C46C]iAlloc+0003AC (??, ??)
    [00170EF0]iGet+0001D0 (??, ??, ??, ??, ??)
    [003E0034]j2_lookup+000454 (??, ??, ??, ??, ??, ??)
    [00588944]vnop_lookup+000184 (??, ??, ??, ??, ??, ??)
    [0054AFA4]lookuppn+000A04
     (??, ??, ??, ??, ??, ??, ??, ??)
    [0054B760]lookupname_internal+0000A0
     (??, ??, ??, ??, ??, ??, ??, ??)
    [0054B884]lookupname_cur+000024
     (??, ??, ??, ??, ??, ??, ??)
    [0059FE14]statx+0001D4 (??, ??, ??, ??)
    
    There is also another thread going through bmIODone:
    (40)> f 15045
    [00537580]slock+000120 (F1000A07A274C7E8,
     F1000815B088C850 [??])
    [00009558].simple_lock+000058 ()
    [00178634]bmIODone+0007D4 (??)
    [0017EF34]internal_iodone_offl+000174 (??, ??)
    [0017ED80]iodone_offl+000080 ()
    [0018255C]i_softmod+00043C ()
    [001AF4EC]flih_util+000258 ()
    

Local fix

  • N/A
    

Problem summary

  • System may crash with a stack trace:
    (40)> f
    pvthread+4B0600 STACK:
     0017E120 bmInodeFlush@AF122_68+000700 (0000000000000000,
     0000000000000280, F1000A200014A000, 0000000003060983,
     0000000000000000, 0000000002C20000, 0000000000000004,
     0000000003060983  ?? )
     0017A138 bmInodeFlush+000038 (??)
     003704EC pagerUnbind@AF66_41+00012C (??, ??, ??, ??)
     0036F5CC pagerUnbind+00002C (??, ??, ??)
     001707A8 iRecycle+000128 (??, ??, ??)
     0016C46C iAlloc+0003AC (??, ??)
     00170EF0 iGet+0001D0 (??, ??, ??, ??, ??)
     003E0034 j2_lookup+000454 (??, ??, ??, ??, ??, ??)
     00588944 vnop_lookup+000184 (??, ??, ??, ??, ??, ??)
     0054AFA4 lookuppn+000A04
     (??, ??, ??, ??, ??, ??, ??, ??)
     0054B760 lookupname_internal+0000A0
     (??, ??, ??, ??, ??, ??, ??, ??)
     0054B884 lookupname_cur+000024
     (??, ??, ??, ??, ??, ??, ??)
     0059FE14 statx+0001D4 (??, ??, ??, ??)
    

Problem conclusion

  • correct serialization of the buffers
    

Temporary fix

Comments

  • 6100-07 - use AIX APAR IV47000
    6100-08 - use AIX APAR IV57775
    6100-09 - use AIX APAR IV50530
    6100-09 - use AIX APAR IV50530
    6100-09 - use AIX APAR IV50530
    7100-01 - use AIX APAR IV57475
    7100-02 - use AIX APAR IV56920
    7100-03 - use AIX APAR IV50840
    

APAR Information

  • APAR number

    IV50530

  • Reported component name

    AIX 610 STD EDI

  • Reported component ID

    5765G6200

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Submitted date

    2013-10-08

  • Closed date

    2013-10-08

  • Last modified date

    2014-08-14

  • APAR is sysrouted FROM one or more of the following:

    IV47000

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    AIX 610 STD EDI

  • Fixed component ID

    5765G6200

Applicable component levels

  • R610 PSY U859304

       UP14/05/21 I 1000

PTF to Fileset Mapping



Document information

More support for: AIX Enterprise Edition

Software version: 610

Operating system(s): AIX

Reference #: IV50530

Modified date: 14 August 2014