Re: Dump debugging without "crash"

From: Justin Bleistein (justin.bleistein_at_TOWERSPERRIN.COM)
Date: 05/26/05

  • Next message: Green, Simon: "Re: Dump debugging without "crash""
    Date:         Thu, 26 May 2005 07:48:24 -0400
    To: aix-l@Princeton.EDU
    
    

    Yes, that will work. If you have the: "/unix"/kernel file which was on the
    system when it crashed. All you have to do it restore it off of the
    "mksysb" to a different file name an invoke crash with the following:
    "crash core_lv_or_file_name /file_name". By default, if you enter crash
    without any kernel
    file specification it goes for: "/unix".

            Some tips. When you start looking into the crash, do a; "stat" to
    see if it's valid. Then do a: "trace -m". This will give you the stack
    traceback.
    The first/top function/sub-routine listed was the last one which was
    running when the system crashed. This should be the IAR call. Then take
    the number
    in the parenthesis next to it/hex usually, and run: "le number". That
    should tell you what device driver/module/extension caused the crash.
    Usually when
    that's the cause, you do an: "lslpp -w device_driver_filename" - usually
    "/usr/lib/drivers/file_name", and upgrade that fileset/lpp to the latest
    level. That's if
    the crash was caused by a device driver.

    Thanks.

    --Justin Richard Bleistein
    AIX Systems Administrator

    "Green, Simon" <Simon.Green@EU.ALTRIA.COM>
    Sent by: IBM AIX Discussion List <aix-l@Princeton.EDU>
    05/26/2005 07:30 AM
    Please respond to
    IBM AIX Discussion List <aix-l@Princeton.EDU>

    To
    aix-l@Princeton.EDU
    cc

    Subject
    Re: Dump debugging without "crash"

    I tried kdb, and it's got the same problem as "crash".
     
    If I knew enough about the AIX internals I guess I could just look at the
    raw data - I used to be able to do that for MVS systems, many moons ago -
    but I don't, so I can't.
     
     
    I do still have a mksysb taken before I started work. Could I restore
    /unix from that (to some other name, of course!) then use that as input to
    the kdb command? e.g. kdb /dev/hd7 /old_unix
     
    If I can find the time I might give that a try.
     

    -- 
    Simon Green  
    Altria ITSC Europe s.a.r.l.
    AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
    New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
     
    N.B. Unsolicited email from vendors will not be appreciated.
    Please post all follow-ups to the list.
    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of 
    Justin Bleistein
    Sent: 26 May 2005 12:13
    To: aix-l@Princeton.EDU
    Subject: Re: Dump debugging without "crash"
    Unfortunately, I don't think so. It needs the correct kernel file to 
    resolve symbols and to have a consistent state of the system at the time 
    of 
    the crash. If there is a way, I'd really like to know. I ran into that 
    once before as well. Because of it I never knew the cause of a system 
    crash. 
            Also, this may be worth it. "kdb" actually existed in some later 
    levels of 4.3.3. Go ahead and try it on that. I highly doubt it though. 
    NOTICE:  This communication may contain confidential, proprietary or 
    legally privileged information. It is intended only for the person(s) to 
    whom it is addressed.  If you are not an intended recipient, you may not 
    use, read, retransmit, disseminate or take any action in reliance upon it. 
    Please notify the sender that you have received it in error and 
    immediately delete the entire communication, including any attachments. 
    Towers Perrin does not encrypt and cannot ensure the confidentiality or 
    integrity of external e-mail communications and, therefore, cannot be 
    responsible for any unauthorized access, disclosure, use or tampering that 
    may occur during transmission.  This communication is not intended to 
    create or modify any obligation, contract or warranty of Towers Perrin, 
    unless the firm clearly expresses such an intent.
    

  • Next message: Green, Simon: "Re: Dump debugging without "crash""

    Relevant Pages