From mboxrd@z Thu Jan  1 00:00:00 1970
From: dhylands@gmail.com (Dave Hylands)
Date: Mon, 5 Sep 2011 00:56:19 -0700
Subject: analysis of kernel panic logs.
In-Reply-To: <CAL7WMDfz1mE_qmjN1NsSkut5BUBedvMhdQUxo76gFZ6SmxiH8Q@mail.gmail.com>
References: <CAL7WMDfF6zVExsp1iw9BnzTSsuvwskqF9CL9XX6oe5szs0WLSQ@mail.gmail.com>
	<CAGdaadYPBaV5vM2_YuUhb_q_x0-bYxS8UaoAxxM9LAHxOYW_RA@mail.gmail.com>
	<CAL7WMDd0ZVvpXZ2Bf-efSMDCa1RXEiuw9ennm-PTpg4Cez1jCA@mail.gmail.com>
	<CABi1daHOcKG=msZADUgxL1B4CTdcCCsijQ+GhvrtQvM=-6jxeg@mail.gmail.com>
	<CAL7WMDfz1mE_qmjN1NsSkut5BUBedvMhdQUxo76gFZ6SmxiH8Q@mail.gmail.com>
Message-ID: <CABi1daFA8Mo8A1-AQCDeUC0arbdanw4dDCT1eFaM9-uBu24mug@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hi Sandeep,

On Sun, Sep 4, 2011 at 10:51 PM, sandeep kumar
<coolsandyforyou@gmail.com> wrote:
> Hi Dave,
>
> The problem is solved.
> But i have one doubt.
>
>>So the PC is 0, and the LR is C92F. That tells me that the code at
>>C92F in your init process is trying to call a function through a NULL
>>pointer. You can try disassembling your init process. Something like
>
>>arm-eabi-objdump --disassemble init
>
> In this case we came to know the process name 'init'. But in some
> cases we might just have the link register address, and no process name.
> say some user-space process has caused the panic.
>
> Can u tell me ..how to debug in that case?

You should always have a pid & process name if its a user-space app
which dies (at least if you enable CONFIG_DEBUG_USER and enabling
user_debug)

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com