From: Breno Leitao <leitao@linux•vnet.ibm.com>
To: linuxppc-dev@lists•ozlabs.org
Subject: INIT: PANIC: segmentation violation! sleeping for 30 seconds.
Date: Mon, 26 Oct 2009 15:01:36 -0200 [thread overview]
Message-ID: <4AE5D5F0.9020805@linux.vnet.ibm.com> (raw)
Hi,
I just put a upstream kernel(rc5) on a specific machine I have (Power5), and I got
the following error:
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
init has generated signal 11 but has no handler for it
init used greatest stack depth: 6240 bytes left
Kernel panic - not syncing: Attempted to kill init!
Call Trace:
[c0000001c6e7f920] [c000000000012588] .show_stack+0x6c/0x194 (unreliable)
[c0000001c6e7f9d0] [c000000000088bd4] .panic+0x74/0x1c0
[c0000001c6e7fa60] [c00000000008cbdc] .do_exit+0x43c/0x82c
[c0000001c6e7fb20] [c0000000000286f4] ._exception+0x1d4/0x204
[c0000001c6e7fcf0] [c0000000004e7dc8] .do_page_fault+0x4fc/0x634
[c0000001c6e7fe30] [c00000000000560c] handle_page_fault+0x20/0x74
Downgrading to rc2 shows the same result. Interesting enough, this is the only
machine that fails with the upstream kernel.
Have anyone seen anything similar ?
Thanks
reply other threads:[~2009-10-26 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4AE5D5F0.9020805@linux.vnet.ibm.com \
--to=leitao@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox