From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] RTDM timerbench problems
Date: Wed, 4 Jan 2006 18:19:51 +0100 [thread overview]
Message-ID: <17340.951.310449.498691@domain.hid> (raw)
In-Reply-To: <1136391676.5443.57.camel@domain.hid>
Stelian Pop wrote:
> Before hanging, sometimes it just prints:
> Unable to handle kernel NULL pointer dereference at virtual address 0000004d
>
> Sometimes the oops is more complete (note that sometimes it also hangs in the middle of
> the printout):
> Unable to handle kernel NULL pointer dereference at virtual address 0000004d
> pgd = c0004000
> [0000004d] *pgd=00000000
> Internal error: Oops: 817 [#1]
> Modules linked in: xeno_timerbench
> CPU: 0
> PC is at xnpod_schedule+0x6b4/0x7f0
> LR is at xnpod_schedule+0x54c/0x7f0
> pc : [<c0056cc4>] lr : [<c0056b5c>] Not tainted
> sp : c7d41830 ip : c79e8044 fp : c7d41860
> r10: c0283c2c r9 : c0282
>
> Does this rings a bell to someone ?
Not much, but two remarks:
- last summer, there use to be such a problem on x86 because of some
wrong FPU switch. So, is FPU enabled ? Are you compiling latency with
-msoft-float ?
When announcing the ARM Adeos port, you told us that not all
exceptions were trapped by the Adeos patch. If one of the FPU
exceptions is not trapped, it would explain why we do not get the
usual message "Invalid use of FPU at ..." before the oops.
- as far as I know, xnpod_schedule never recurses, so, there is little
chance for PC and LR to be both in xnpod_schedule. If I am not wrong,
it means that you will have to have a look at the disassembly (sorry)
and see in really what functions the bugs happen. Sometimes the -r and
-S option of objdump help...
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-01-04 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 16:21 [Xenomai-core] RTDM timerbench problems Stelian Pop
2006-01-04 16:49 ` Jan Kiszka
2006-01-04 17:10 ` Stelian Pop
2006-01-04 17:19 ` Gilles Chanteperdrix [this message]
2006-01-04 17:28 ` Stelian Pop
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=17340.951.310449.498691@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--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.