AIX

AIX

Connect with fellow AIX users and experts to gain knowledge, share insights, and solve problems.

 View Only
Back to discussions
Expand all | Collapse all

System crash in xmalloc

  • 1.  System crash in xmalloc

    Posted Sun August 01, 2010 11:46 PM

    Originally posted by: MuppanaLalitaPrasad


    (0)> stat
    SYSTEM_CONFIGURATION:
    CHRP_SMP_PCI POWER_PC POWER_4 machine with 1 available CPU(s) (64-bit registers)

    SYSTEM STATUS:
    sysname... AIX
    nodename.. aix87
    release... 3
    version... 5
    build date Dec 1 2004
    build time 15:08:28
    label..... yes
    machine... 000D772C4C00
    nid....... 0D772C4C
    time of crash: Sat Jul 31 06:00:24 2010
    age of system: 1 day, 55 min., 13 sec.
    xmalloc debug: disabled

    CRASH INFORMATION:
    CPU 0 CSA F000000030077780 at time of crash, error code for LEDs: 30000000
    pvthread+001600 STACK:
    00300518frmalloc+00039C (F100080000000318, 00000000000522AC,
    0000000000000009, 00000000000522B0, 0000000000016037 ??)
    002FF0F4xmalloc1+0003E8 (??, ??, ??, ??, ??, ??, ??, ??)
    00304968xmalloc+000264 (??, ??, ??)
    042716F8inm_save_bufinfo+000118 (F10008000E600000, 0FFFFFFFF4077570,
    0FFFFFFFF40779D0)
    042724D0my_own_ddstrategy+000368 (F100011978001200)
    000A81D4std_devstrat+000240 (??)
    000A8378devstrat+000074 (??)
    03CBE174hd_start_10_2+0001A0 (??)
    03CCED1Chd_strategy+0000D4 (??)
    000A81D4std_devstrat+000240 (??)
    000A8378devstrat+000074 (??)
    00212A94j2PagerService+0005B8 (??)
    0020FC8Cj2PagerThread+0001EC (??)
    00119B50threadentry+000014 (??, ??, ??, ??)
    (0)>

    Recursive call to xmalloc causes hang or crash in frmalloc on recursive lock acquisition. This what I found from http://www-01.ibm.com/support/docview.wss?uid=isg1IZ65498

    So can any one please verify whether this statement is applicable for AIX 5.3 also or not??


  • 2.  Re: System crash in xmalloc

    Posted Mon November 08, 2010 05:46 PM

    Originally posted by: Red.Wilder


    {$author} wrote:
    {$content}

    Maybe it's a bug, You can submit it to the MS connect.


Related Content