IBM Support

LO65912: SERVER CRASH PANIC INVALID POOL FREE CHAIN

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The server crashed with Panic Invalid pool free chain with no
    database reported in the Vthread.
    
    Memory corruption was suspected so the customer was asked to add
    the debug_checkmarkers=1.
    
    [2150592:01148-55256] DPOOL CORRUPTION DETECTED - handle =
    0x00000000, type = 0x814E, size = 0x00800000, ptr = 0x96000800
    
    [2150592:01148-55256] DPOOL - prev->next = 0x000000DC
    pptr->next = 0x0001519C
    
    [2150592:01148-55256] DPOOL - pptr->signature = 0xDDDD162E
    valid dfree_signature = 0xDDDD162E
    
    PANIC: Invalid pool free chain
    
    ###################################
    ## thread 216/258 :: server pid=2150592, k-id=unning  2,
    pthr-id=55256
    ## stack          :: k-state=wait, stk max-size=269208,
    cur-size=10344
    ###################################
    ptrgl._ptrgl() at 0x200003d0
    raise.nsleep(??, ??) at 0x2002057c
    sleep(??) at 0x200d4294
    OSRunExternalScript(0x35984ef0, 0x1) at 0x213bf60c
    OSFaultCleanupExt(0x0, 0x1000, 0x0, 0x0, 0x0, 0x0) at 0x213bed9c
    OSFaultCleanup(0x0, 0x1000, 0x0) at 0x213c0888
    fatal_error(0xb, 0x359854ac, 0x35985220) at 0x219a9310
    pthread_kill(??, ??) at 0x202f36f4
    _p_raise(??) at 0x202f3164
    raise.raise(??) at 0x20020910
    Panic(0x359857bc) at 0x2035b8b0
    HandleBadFreeChain(0x96000800) at 0x21a42c8c
    AllocDBlock(0x2433a2e8, 0xff82, 0x35986054) at 0x21a4348c
    OSAllocDBlock(0x2433a2e8, 0xff82, 0x35986054) at 0x21a43a6c
    DPoolAlloc(0xf0000010, 0xff82, 0x8a19, 0xfff3c2c0) at 0x20493490
    AllocObject(0xf0000010, 0x245ef018, 0xfff3c2b0, 0xff82, 0x6,
    0x8a19) at 0x20493be0
    OSMemAllocExtended(0x8a19, 0xff7c, 0x0, 0x35986352) at
    0x20494bb0
    OSCreatePool(0x8a19ca19, 0x0, 0x20e020e, 0xff7c0400, 0x0,
    0xff7c0000, 0x359863c0) at 0x2053ee78
    NSFNoteCreatePoolExtended(0x0, 0x8a198a19, 0x4000000, 0x0, 0x20,
    0x35986470) at 0x2053c754
    InitLogEntry(0x3598650c, 0x1418c, 0xd000d, 0x1010c4f0) at
    0x205318e0
    LogCreateEntry(0x1010c4f0, 0x35986682) at 0x2053c36c
    DbServerTerm(0x3f9a223, 0x1e47b0) at 0x1008dca8
    DeleteTask(0x4bf01c, 0x1) at 0x10016e64
    WorkThreadTask(0x96a221, 0x0) at 0x100b0230
    Scheduler(0x0) at 0x100c3974
    ThreadWrapper(0x0) at 0x204958d4
    
    
    After adding the debug_checkmarkers=1 the server start to crash
    with PANIC: CheckMarkers: Memory following object has been
    destroyed
    
    [1892526:00233-17734] CheckMarkers: Segment length: 65542
    [1892526:00233-17734] 00000000: 0272 FFFE 0000
    '.r.~..'
    
    
    [1892526:00233-17734]  TID=[1892526:00233-17734]/K-TID=819301
    Stack base=0x322DEE50, Stack size = 7008 bytes
    PANIC: CheckMarkers: Memory following object has been destroyed
    
    ###################################
    ## thread  70/156 :: server pid=1892526, k-id= 819301  ,
    pthr-id=17734
    ## stack          :: k-state=run, stk max-size=269208,
    cur-size=11432
    ###################################
    _p_nsleep(??, ??) at 0x202f3294
    raise.nsleep(??, ??) at 0x2002057c
    sleep(??) at 0x200d4294
    OSRunExternalScript(0x322dcaf0, 0x1) at 0x213bf60c
    OSFaultCleanupExt(0x0, 0x1000, 0x0, 0x0, 0x0, 0x0) at 0x213bed9c
    OSFaultCleanup(0x0, 0x1000, 0x0) at 0x213c0888
    fatal_error(0xb, 0x322dd0ac, 0x322dce20) at 0x219a9310
    pthread_kill(??, ??) at 0x202f36f4
    _p_raise(??) at 0x202f3164
    raise.raise(??) at 0x20020910
    Panic(0x322dd3bc) at 0x2035b8b0
    CheckMarkers(0xd59a1178, 0x10006) at 0x2032c354
    CheckDescMarkers(0xffeb6980) at 0x2032c23c
    OSUnlockObject(0x1cbf1cbf) at 0x2032cf68
    DbGetReplicaMatches(0x322de4d8, 0x1c5b1c5b, 0x8d008d, 0x0,
    0x322de590, 0xd2a10a70, 0xd2a10a6c) at 0x20727140
    iNSFDbGetReplicaMatches(0x322de4d8, 0x1c5b1c5b, 0x8d008d, 0x0,
    0x322de590, 0xd2a10a70, 0xd2a10a6c) at 0x2083c30c
    NSFDbGetReplicaMatches(0x3a203a2, 0x1c5b1c5b, 0x8d008d, 0x0,
    0x322de590, 0xd2a10a70, 0xd2a10a6c) at 0x2082a05c
    ServerGetReplicaMatches(0x222a8, 0x165d4) at 0x100644bc
    DbServer(0xb17b0c, 0x222a8) at 0x10015774
    WorkThreadTask(0x497b00, 0x0) at 0x100b0038
    Scheduler(0x0) at 0x100c3974
    ThreadWrapper(0x0) at 0x204958d4
    ./tmpfiles.1884368.scr: 425: warning: Thread is in kernel mode,
    not all registers can be accessed.
    

Local fix

Problem summary

  • A programming error was found and will be corrected in a future
     release.
    

Problem conclusion

  • A programming error was found and will be corrected in a future
     release.
    

Temporary fix

Comments

  • This APAR is associated with SPR# MALK8PBLM5.
    

APAR Information

  • APAR number

    LO65912

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    853

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-07

  • Closed date

    2012-05-07

  • Last modified date

    2012-05-07

  • 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

    DOMINO SERVER

  • Fixed component ID

    5724E6200

Applicable component levels

  • R853 PSN

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.3","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
07 May 2012