From: coolsandyforyou@gmail.com (sandeep kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: analysis of kernel panic logs.
Date: Fri, 2 Sep 2011 11:33:33 +0530 [thread overview]
Message-ID: <CAL7WMDfF6zVExsp1iw9BnzTSsuvwskqF9CL9XX6oe5szs0WLSQ@mail.gmail.com> (raw)
Hi,
im working on android, kernel version 2.6.35.11
I got these logs showing kernel panic and the target is rebooting.
>From the logs i understood in init process something is causing kernel
panic.
<3>[ 85.235589] init: [boot time] processing action 0x4c5e8
(property:init.svc.samsungani=stopped)
<3>[ 85.236565] init: [boot time] processing action 0x4ef20
(property:init.svc.samsungani=stopped)
<0>[ 85.236840] Kernel panic - not syncing: Attempted to kill init!
<4>[ 85.236932] [<c01076b8>] (unwind_backtrace+0x0/0x164) from
[<c072436c>] (panic+0x6c/0xec)
<4>[ 85.237023] [<c072436c>] (panic+0x6c/0xec) from [<c01a931c>]
(do_exit+0x70/0x6a0)
<4>[ 85.237115] [<c01a931c>] (do_exit+0x70/0x6a0) from [<c01a99dc>]
(do_group_exit+0x90/0xc0)
<4>[ 85.237176] [<c01a99dc>] (do_group_exit+0x90/0xc0) from [<c01b8fc4>]
(get_signal_to_deliver+0x3e0/0x424)
<4>[ 85.237267] [<c01b8fc4>] (get_signal_to_deliver+0x3e0/0x424) from
[<c01039d8>] (do_signal+0x68/0x640)
<4>[ 85.237359] [<c01039d8>] (do_signal+0x68/0x640) from [<c0103fc8>]
(do_notify_resume+0x18/0x38)
<4>[ 85.237450] [<c0103fc8>] (do_notify_resume+0x18/0x38) from
[<c0100bd0>] (work_pending+0x1c/0x20)
<0>[ 85.237542] Rebooting in 5 seconds..
<2>[ 85.237572] CPU0: stopping
<4>[ 85.237603] [<c01076b8>] (unwind_backtrace+0x0/0x164) from
[<c0100338>] (do_IPI+0xd8/0x154)
<4>[ 85.237695] [<c0100338>] (do_IPI+0xd8/0x154) from [<c0728188>]
(__irq_usr+0x48/0xe0)
<4>[ 85.237756] Exception stack(0xdc18dfb0 to 0xdc18dff8)
<4>[ 85.237817] dfa0: 00000000
0000007c 00000000 4097b240
<4>[ 85.237878] dfc0: 45957cfe 4ba95bd8 4fc24a48 000000f4 80118200
ffffe9f4 00000000 801a6374
<4>[ 85.237939] dfe0: 000000f4 4fc249f8 8011d0a8 8011bf18 20000010
ffffffff
But how to interpret the Exception stack, dfa0 etc., to narrow down what
exactly caused the panic.
And in similer cases when oops happens also we will get the register dump, i
know how to interpret PC, but what about the rest of the registers.
how they are useful in analysing the situation.
--
With regards,
Sandeep Kumar Anantapalli,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110902/fba32c07/attachment.html
next reply other threads:[~2011-09-02 6:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 6:03 sandeep kumar [this message]
2011-09-02 7:26 ` analysis of kernel panic logs Mulyadi Santosa
2011-09-02 11:11 ` sandeep kumar
2011-09-02 13:12 ` keshav yadav
2011-09-02 15:13 ` Dave Hylands
2011-09-05 5:51 ` sandeep kumar
2011-09-05 7:56 ` Dave Hylands
2011-09-05 8:37 ` sandeep kumar
2011-09-06 16:44 ` Dave Hylands
2011-09-06 16:56 ` anish singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL7WMDfF6zVExsp1iw9BnzTSsuvwskqF9CL9XX6oe5szs0WLSQ@mail.gmail.com \
--to=coolsandyforyou@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.