From: Philippe Gerum <rpm@xenomai.org>
To: niklaus.giger@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Problem with periodic timer on PPC40x solved
Date: Tue, 26 Sep 2006 21:48:39 +0200 [thread overview]
Message-ID: <1159300119.5084.173.camel@domain.hid> (raw)
In-Reply-To: <200609262134.48627.niklaus.giger@domain.hid>
On Tue, 2006-09-26 at 21:34 +0200, Niklaus Giger wrote:
> Here is the stack with adeos-ipipe 1.3 after applying your patch
>
> (gdb) info stack
> #0 xnpod_fault_handler (fltinfo=0xc1489e18) at
> kernel/xenomai/nucleus/pod.c:216
> #1 0xc004bad4 in xnpod_trap_fault (fltinfo=0x73) at
> kernel/xenomai/nucleus/pod.c:2907
> #2 0xc0043ee8 in xnarch_trap_fault (event=115, domid=0, data=0xc01a9435) at
> include/asm/xenomai/bits/init.h:46
> #3 0xc012dc38 in exception_event (event=3223286668, ipd=0x0, data=0xc01a9435)
> at arch/ppc/xenomai/hal.c:385
> #4 0xc003fe18 in __ipipe_dispatch_event (event=0, data=0xc1489f50) at
> kernel/ipipe/core.c:665
> #5 0xc000aecc in do_page_fault (regs=0xc1489f50, address=268448708,
> error_code=0) at include/linux/ipipe.h:445
> #6 0xc0003258 in handle_page_fault ()
The function parameters look weird, but the backtrace seems ok. This
tells us that it's not related to FPU emulation, but rather to an
invalid memory access.
> Previous frame inner to this frame (corrupt stack?)
> (gdb)
>
> Hope it helps you
--
Philippe.
next prev parent reply other threads:[~2006-09-26 19:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 18:13 [Xenomai-core] Problem with periodic timer on PPC40x identified Niklaus Giger
2006-09-23 20:55 ` Wolfgang Grandegger
2006-09-23 21:33 ` Philippe Gerum
2006-09-24 20:47 ` [Xenomai-core] Problem with periodic timer on PPC40x solved Niklaus Giger
2006-09-24 21:07 ` Wolfgang Grandegger
2006-09-25 15:57 ` Philippe Gerum
2006-09-25 20:29 ` Niklaus Giger
2006-09-25 20:59 ` Philippe Gerum
2006-09-25 21:15 ` Niklaus Giger
2006-09-26 6:59 ` Philippe Gerum
2006-09-26 14:21 ` Philippe Gerum
2006-09-26 18:39 ` Niklaus Giger
2006-09-26 19:34 ` Niklaus Giger
2006-09-26 19:48 ` Philippe Gerum [this message]
2006-09-26 6:47 ` Wolfgang Grandegger
-- strict thread matches above, loose matches on Subject: below --
2006-09-26 14:56 gilles.chanteperdrix
2006-09-26 16:10 ` Philippe Gerum
2006-09-26 16:28 ` Wolfgang Grandegger
2006-09-26 16:38 ` Philippe Gerum
2006-09-26 16:57 ` Wolfgang Grandegger
2006-09-26 18:56 ` Niklaus Giger
2006-09-26 20:23 ` Wolfgang Grandegger
2006-09-26 21:26 ` Niklaus Giger
2006-09-27 10:13 ` Wolfgang Grandegger
2006-09-27 18:19 ` Wolfgang Grandegger
2006-09-28 6:02 ` Niklaus Giger
2006-09-28 7:59 ` Wolfgang Grandegger
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=1159300119.5084.173.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=niklaus.giger@domain.hid \
--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.