From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Porting xenomai 2.6.3 and ipipe to 3.12 kernel
Date: Mon, 31 Mar 2014 20:12:37 +0200 [thread overview]
Message-ID: <5339B015.3080008@xenomai.org> (raw)
In-Reply-To: <20140331174555.GO17765@csclub.uwaterloo.ca>
On 03/31/2014 07:45 PM, Lennart Sorensen wrote:
> Does anyone have any hints on how to track this down, or even for how
> to properly test that moving to 3.12 is actually working.
On what platform do you get this? If on cortex A8, and the user-space is
compiled in thumb2 mode, note that an erratum workaround is needed,
flushing the BTB at each context switch to avoid problem when ARM code
is replaced by THUMB code at the same (virtual) address when switching
context.
My advice would be to wait, Philippe is currently merging the I-pipe git
with 3.14 (you can actually find the 3.12 merge in my git tree, under
the branch raw/for-ipipe-3.12.0, it has been lightly tested though, as I
wait for 3.14 to be ready to test more thoroughly).
If you can not wait, then you can enable CONFIG_DEBUG_USER, and pass
user_debug=29 on the kernel command line, to have a complete a dump upon
fault (and notably in the case of SIGILL). You can also extend this dump
by using a hack done in the FCSE patch to print the equivalent of a dump
of /proc/self/maps with markers indicating where the PC, SP, and fault
address are when a fault occurs.
--
Gilles.
next prev parent reply other threads:[~2014-03-31 18:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 17:45 [Xenomai] Porting xenomai 2.6.3 and ipipe to 3.12 kernel Lennart Sorensen
2014-03-31 18:12 ` Gilles Chanteperdrix [this message]
2014-03-31 18:24 ` Lennart Sorensen
2014-03-31 19:15 ` Lennart Sorensen
2014-03-31 19:17 ` Gilles Chanteperdrix
2014-03-31 19:18 ` Lennart Sorensen
2014-03-31 19:37 ` Lennart Sorensen
2014-03-31 19:44 ` Gilles Chanteperdrix
2014-03-31 20:42 ` Lennart Sorensen
2014-03-31 20:53 ` Lennart Sorensen
2014-03-31 20:57 ` Lennart Sorensen
2014-03-31 21:06 ` Gilles Chanteperdrix
2014-03-31 21:25 ` Lennart Sorensen
2014-03-31 21:49 ` Gilles Chanteperdrix
2014-03-31 21:53 ` Lennart Sorensen
2014-03-31 21:59 ` Lennart Sorensen
2014-03-31 22:04 ` Lennart Sorensen
2014-03-31 22:11 ` Gilles Chanteperdrix
2014-03-31 22:27 ` Gilles Chanteperdrix
2014-04-01 1:32 ` Lennart Sorensen
2014-04-01 10:52 ` Gilles Chanteperdrix
2014-04-01 13:12 ` Lennart Sorensen
2014-04-01 19:35 ` Gilles Chanteperdrix
2014-04-01 19:40 ` Lennart Sorensen
2014-04-01 20:52 ` Gilles Chanteperdrix
2014-04-01 21:45 ` Lennart Sorensen
2014-04-01 22:01 ` Gilles Chanteperdrix
2014-04-02 2:35 ` Lennart Sorensen
2014-04-02 7:11 ` Gilles Chanteperdrix
2014-04-02 13:24 ` Lennart Sorensen
2014-04-02 13:26 ` Gilles Chanteperdrix
2014-04-02 13:40 ` Lennart Sorensen
2014-04-02 13:41 ` Lennart Sorensen
2014-04-02 13:46 ` Lennart Sorensen
2014-04-02 13:56 ` Gilles Chanteperdrix
2014-04-02 14:38 ` Lennart Sorensen
2014-04-02 14:41 ` Gilles Chanteperdrix
2014-04-03 13:46 ` Lennart Sorensen
2014-04-03 13:56 ` Gilles Chanteperdrix
2014-04-03 14:16 ` Lennart Sorensen
2014-04-14 21:06 ` Lennart Sorensen
2014-04-15 11:39 ` Gilles Chanteperdrix
2014-06-13 18:15 ` Lennart Sorensen
2014-03-31 19:19 ` Gilles Chanteperdrix
[not found] <mailman.33.1396388743.2839.xenomai@xenomai.org>
2014-04-02 9:21 ` Andreas Glatz
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=5339B015.3080008@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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.