From: Philippe Gerum <rpm@xenomai.org>
To: Henry Bausley <hbausley@deltatau.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Kernel Panic not syncing kernel stack overflow on AMCC PowerPC 460EX upon upgrade
Date: Wed, 26 Jun 2013 19:00:28 +0200 [thread overview]
Message-ID: <51CB1E2C.2000302@xenomai.org> (raw)
In-Reply-To: <1372258188.12144.161.camel@lx-henry>
On 06/26/2013 04:49 PM, Henry Bausley wrote:
>
>
> I am attempting to upgrade to Xeno 2.6.2.1 / Ipipe 3.2.21 from
> a working Xeno 2.5.6 / Ipipe 2.6.30.3 configuration
>
> I am getting a Kernel Panic not syncing kernel stack overflow errors
> with the new kernel.
>
> The application is a kernel module that operates soley from interrupts
> and communicates to user space with applications with shared memory. It
> has been running with the earlier kernels without issues for many years.
> Below are the messages I get when the system crashes.
>
> If anyone has any hints based upon the data when it crashes below it
> would be greatly appreciated.
>
>
<snip>
> Call
> Trace:
> [8049bef0] [80006c00] show_stack+0x54/0x154
> (unreliable)
> [8049bf30] [8001a26c] __schedule_bug
> +0x68/0x6c
> [8049bf40] [80372b1c] __schedule
> +0x3e8/0x430
> [8049bf90] [80007738] cpu_idle
> +0xd8/0xdc
> [8049bfb0] [80001bd4] rest_init
> +0x64/0x78
> [8049bfc0] [8044a770] start_kernel
> +0x2d0/0x2e4
> [8049bff0] [80000044] _start
> +0x44/0x88
> Kernel panic - not syncing: kernel stack overflow
This is typical of some code badly trashing the linux interrupt state
when running in primary domain. The idle loop breakage may be a
collateral damage of such issue.
Could you tell us a bit more about your kernel config, e.g.
- which preemption model?
- did you enable CONFIG_IPIPE_DEBUG_INTERNAL? otherwise, do you have any
warning notice when set?
--
Philippe.
next prev parent reply other threads:[~2013-06-26 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 14:49 [Xenomai] Kernel Panic not syncing kernel stack overflow on AMCC PowerPC 460EX upon upgrade Henry Bausley
2013-06-26 17:00 ` Philippe Gerum [this message]
2013-06-27 22:24 ` Henry Bausley
2013-06-26 17:20 ` Gilles Chanteperdrix
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=51CB1E2C.2000302@xenomai.org \
--to=rpm@xenomai.org \
--cc=hbausley@deltatau.com \
--cc=xenomai@xenomai.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.